January 2019
Intermediate to advanced
286 pages
7h 41m
English
A lot of InnoDB mutexes and rw-locks are reserved for a short time. On a server with multiple cores, you will have more advantages if a thread is constantly checking whether it can acquire a mutex or rw-lock for a while before going to sleep.
You can control the maximum delay in this case between testing a mutex and an rw-lock by using the innodb_spin_wait_delay parameter.
For example, on a server where all processors share a fast cache, you can reduce the delay or disable the busy loop completely if you change the innodb_spin_wait_delay variable to 0, which will help to improve the performance of your database.
Read now
Unlock full access