Shulou(Shulou.com)05/31 Report--

How to improve high concurrent MySQL performance by banning deadlock detection is not very clear to many beginners. In order to help you solve this problem, the following editor will explain it in detail. People with this need can come and learn. I hope you can get something.

On a highly concurrent MySQL server, transactions recursively detect deadlocks, and when beyond a certain depth, performance degradation becomes unacceptable. FACEBOOK has long proposed a ban on deadlock detection.

We did an experiment where TPS was greatly improved after deadlock detection was disabled, as shown in the following figure:

After deadlock detection is disabled, even if a deadlock occurs, the transaction will not be rolled back, but all wait until the timeout

Patch is relatively simple, just add a layer of judgment before deadlock detection:

If (innobase_deadlock_check & & UNIV_UNLIKELY (lock_deadlock_occurs (lock, trx)

.

Innobase_deadlock_check is a new system variable added to innodb to control whether deadlock detection is turned on.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

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.