This document provides an overview of techniques for diagnosing and troubleshooting performance and other issues with the InnoDB storage engine in MySQL. It discusses sources of diagnostic information like SHOW ENGINE INNODB STATUS and various status variables. Common problems covered include data dictionary issues, crashing, locking, and performance problems related to disk I/O, tablespace usage, CPU usage, and thread thrashing. Interpreting diagnostic information and potential solutions are provided for each type of issue.

1. Mastering InnoDB Diagnostics Harrison Fisk Senior Principal Technical Support Engineer

5. Information Sources

7. InnoDB monitors

8. SHOW GLOBAL STATUS

11. Gdb ( Poor mans profiler (PMP))

12. OS specific tools

16. InnoDB plugin

17. XtraDB

18. Data Dictionary

20. Can't drop and/or create tables or databases

21. Example errors:

23. Output to error log

24. CREATE TABLE innodb_table_monitor (id int) ENGINE=innodb;

26. DB_TRX_ID

30. Remove them

31. Crashing

41. Memory image produced

42. Requires exactly the same binary and libraries

43. With rpm ensure debuginfo is installed

44. Non-stripped binaries

47. Windows: Minidump/DrWatson/Windbg

51. Locking

57. Index

62. Performance

68. 2 Write every commit

69. 0 Write only every second

74. Change innodb_flush_log_at_trx_commit

76. Faster writes

80. await

82. Increase innodb_buffer_pool_size

83. New LRU algorithm in InnoDB plugin

94. MySQL 5.5

100. Questions?

101. The presentation is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.