Shulou(Shulou.com)06/01 Report--

Because InnoDB storage engine implements row-level locking, although the performance loss caused by the implementation of locking mechanism may be higher than that of table-level locking, it is much better than MyISAM's table-level locking in terms of overall concurrency processing capacity. When the system concurrency is high, the overall performance of InnoDB is compared with that of MyISAM.

There will be a more obvious advantage. But InnoDB's row-level locking also has its fragile side, and when we use it improperly, it may make the overall performance of InnoDB not only not better than MyISAM, but even worse.

In order to make rational use of InnoDB row-level locking and enhance our strengths and avoid weaknesses, we must do the following work:

(1)。 Let all data retrieval be done through the index Index as much as possible, so as to prevent InnoDB from upgrading to table-level locking because it cannot be locked by the index key.

(2)。 Reasonably design the index, let InnoDB lock on the index key as accurately as possible, narrow the locking range as much as possible, and avoid causing unnecessary locking and affecting the execution of other queries.

(3)。 Minimize the filtering conditions of range-based data retrieval to avoid locking records that should not be locked because of the negative effects of gap locks.

(4)。 Try to control the size of MySQL transactions, reduce the amount of locked resources and the length of time locked.

(5)。 As far as the business environment allows, try to use a lower level of transaction isolation to reduce the additional cost of implementing the transaction isolation level for MySQL.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.