content_image/693312.jpg
| wait/synch/mutex/innodb/trx_sys_mutex | NO | NO | | wait/synch/mutex/innodb/zip_pad_mutex | NO | NO | | wait/synch/mutex/innodb/master_key_id_mutex | NO | NO | +---------------------------------------------------------+---------+-------+ 

2. Some InnoDB  mutex instances are created at server startup and are only instrumented if the associated instrument is also enabled at server startup. To ensure that all InnoDB  mutex instances are instrumented and enabled, add the following performance-schema-instrument  rule to your MySQL configuration file: 

performance-schema-instrument=’wait/synch/mutex/innodb/%=ON’ 

If you do not require wait event data for all InnoDB  mutexes, you can disable specific instruments by adding additional performance-schema-instrument  rules to your MySQL configuration file. For example, to disable InnoDB  mutex wait event instruments related to full-text search, add the following rule: 

performance-schema-instrument=’wait/synch/mutex/innodb/fts%=OFF’ 

<img src='content_image/693312.jpg'>

## Note 

Rules with a longer prefix such as wait/synch/mutex/innodb/fts%  take precedence over rules with shorter prefixes such as wait/synch/mutex/ innodb/% . 

After adding the performance-schema-instrument  rules to your configuration file, restart the server. All the InnoDB  mutexes except for those related to full text search are enabled. To verify, query the setup_instruments  table. The ENABLED  and TIMED  columns should be set to YES  for the instruments that you enabled. 

mysql> SELECT * FROM performance_schema.setup_instruments WHERE NAME LIKE ’%wait/synch/mutex/innodb%’; +-------------------------------------------------------+---------+-------+ | NAME | ENABLED | TIMED | +-------------------------------------------------------+---------+-------+ | wait/synch/mutex/innodb/commit_cond_mutex | YES | YES | | wait/synch/mutex/innodb/innobase_share_mutex | YES | YES | | wait/synch/mutex/innodb/autoinc_mutex | YES | YES | ... | wait/synch/mutex/innodb/master_key_id_mutex | YES | YES | +-------------------------------------------------------+---------+-------+ 49 rows in set (0.00 sec) 

3. Enable wait event consumers by updating the setup_consumers  table. Wait event consumers are disabled by default. 

mysql> UPDATE performance_schema.setup_consumers SET enabled = ’YES’ WHERE name like ’events_waits%’; Query OK, 3 rows affected (0.00 sec) Rows matched: 3 Changed: 3 Warnings: 0 

You can verify that wait event consumers are enabled by querying the setup_consumers  table. The events_waits_current , events_waits_history , and events_waits_history_long consumers should be enabled. 

mysql> SELECT * FROM performance_schema.setup_consumers; +----------------------------------+---------+ | NAME | ENABLED | +----------------------------------+---------+ | events_stages_current | NO | 

