- 1 Performance Schema Quick Start
- 2 Performance Schema Configuration
- 3 Performance Schema Status Monitoring
- 4 Performance Schema Event Timing
- 5 Performance Schema Event Instrument Naming Conventions
- 6 Performance Schema Table General Characteristics
- 7 Performance Schema Table Descriptions
- 8 Performance Schema and Plugins
- 9 Performance Schema System Variables
- 10 Performance Schema Status Variables
- 11 Using Performance Schema to Diagnose Problems
- 12 Performance Schema Restrictions
- 13 Other Changes to Manual
[+/-]
Tables in the performance_schema database can
be grouped as follows:
Setup tables. These tables are used to configure and display monitoring characteristics.
Current events table. The
EVENTS_WAITS_CURRENTtable contains the most recent event for each thread.-
History tables. These tables have the same structure as
EVENTS_WAITS_CURRENTbut contain more rows. TheEVENTS_WAITS_HISTORYtable contains the most recent 10 events per thread.EVENTS_WAITS_HISTORY_LONGcontains the most recent 10,000 events.To change the sizes of these tables, set the
performance_schema_events_waits_history_sizeandperformance_schema_events_waits_history_long_sizesystem variables at server startup. Summary tables. These tables contain information aggregated over all events, including those that have been discarded from the history tables.
Instance tables. These tables document what types of objects are instrumented. An instrumented object, when used by the server, produces an event. These tables provide event names and explanatory notes or status information.
Miscellaneous tables. These do not fall into any of the other table groups.
