Starting with InnoDB 1.1 with MySQL 5.5, you can profile certain internal InnoDB operations using the MySQL Performance Schema feature. This type of tuning is primarily for expert users, those who push the limits of MySQL performance, read the MySQL source code, and evaluate optimization strategies to overcome performance bottlenecks. DBAs can also use this feature for capacity planning, to see whether their typical workload encounters any performance bottlenecks with a particular combination of CPU, RAM, and disk storage; and if so, to judge whether performance can be improved by increasing the capacity of some part of the system.
To use this feature to examine InnoDB performance:
You must be running MySQL 5.5 or higher with the Performance Schema feature available and enabled, as described in Section 22.2, “Performance Schema Configuration”. Since the Performance Schema feature introduces some performance overhead, you should use it on a test or development system rather than on a production system.
You must be running InnoDB 1.1 or higher.
You must be generally familiar with how to use the
feature, for example to query tables in the
Examine the following kinds of InnoDB objects by querying the
performance_schema tables. The
items associated with InnoDB all contain the substring
innodb in the
For the definitions of the
Section 22.7.3, “Performance Schema Instance Tables”. For the
definitions of the
*_summary_* tables, see
Section 22.7.5, “Performance Schema Summary Tables”. For the
definition of the
thread table, see
Section 22.7.6, “Performance Schema Miscellaneous Tables”. For
the definition of the
*_history_* tables, see
Section 22.7.4, “Performance Schema Wait Event Tables”.
Mutexes in the
mutex_instances table. (Mutexes and
RW-locks related to the
pool are not included in this coverage; the same applies
to the output of the
SHOW ENGINE INNODB
RW-locks in the
File I/O operations in the
Threads in the
During performance testing, examine the performance data in
events_waits_history_long tables. If you
are interested especially in InnoDB-related objects, use the
WHERE EVENT_NAME LIKE '%innodb%' to
see just those entries; otherwise, examine the performance
statistics for the overall MySQL server.
For more information about the MySQL Performance Schema, see Chapter 22, MySQL Performance Schema.