Poor InnoDB performance when "History List" is long
Last updated on MARCH 06, 2017
Applies to:MySQL Server - Version 5.0 and later
Information in this document applies to any platform.
In case of poor InnoDB performance it is required to capture several outputs at least of of following SQL statements:
SHOW /*!50101 ENGINE*/ INNODB STATUS\G
SHOW GLOBAL STATUS;
All analysis in this document refers to outputs of these two commands.
- Poor InnoDB performance
- INNODB STATUS shows long "History List"
- INNODB STATUS shows buffer pool hit rate is less than 980/1000
- GLOBAL STATUS shows quick increase of Innodb_buffer_pool_reads status variable
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms