content_image/771974.jpg
information. For example, the file_instances  table lists instances of instruments for file I/O operations and their associated files: 

mysql> SELECT * FROM performance_schema.file_instances\G *************************** 1. row ***************************  FILE_NAME: /opt/mysql-log/60500/binlog.000007 EVENT_NAME: wait/io/file/sql/binlog OPEN_COUNT: 0 *************************** 2. row ***************************  FILE_NAME: /opt/mysql/60500/data/mysql/tables_priv.MYI EVENT_NAME: wait/io/file/myisam/kfile OPEN_COUNT: 1 *************************** 3. row ***************************  FILE_NAME: /opt/mysql/60500/data/mysql/columns_priv.MYI EVENT_NAME: wait/io/file/myisam/kfile OPEN_COUNT: 1 ... 

Setup tables are used to configure and display monitoring characteristics. For example, setup_instruments  lists the set of instruments for which events can be collected and shows which of them are enabled: 

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

To understand how to interpret instrument names, see Section 27.6, “Performance Schema Instrument Naming Conventions” . 

To control whether events are collected for an instrument, set its ENABLED  value to YES  or NO . For example: 

mysql> UPDATE performance_schema.setup_instruments SET ENABLED = ’NO’ WHERE NAME = ’wait/synch/mutex/sql/LOCK_mysql_create_db’; 

