Documentation Home
MySQL Performance Schema
Related Documentation Download this Excerpt
PDF (US Ltr) - 0.8Mb
PDF (A4) - 0.8Mb
HTML Download (TGZ) - 138.6Kb
HTML Download (Zip) - 156.7Kb


MySQL Performance Schema  /  Performance Schema Table Descriptions

Chapter 10 Performance Schema Table Descriptions

Table of Contents     [+/-]

10.1 Performance Schema Table Index
10.2 Performance Schema Setup Tables     [+/-]
10.3 Performance Schema Instance Tables     [+/-]
10.4 Performance Schema Wait Event Tables     [+/-]
10.5 Performance Schema Stage Event Tables     [+/-]
10.6 Performance Schema Statement Event Tables     [+/-]
10.7 Performance Schema Transaction Tables     [+/-]
10.8 Performance Schema Connection Tables     [+/-]
10.9 Performance Schema Connection Attribute Tables     [+/-]
10.10 Performance Schema User Variable Tables
10.11 Performance Schema Replication Tables     [+/-]
10.12 Performance Schema Lock Tables     [+/-]
10.13 Performance Schema System Variable Tables
10.14 Performance Schema Status Variable Tables
10.15 Performance Schema Summary Tables     [+/-]
10.16 Performance Schema Miscellaneous Tables     [+/-]

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 tables. The events_waits_current table contains the most recent event for each thread. Other similar tables contain current events at different levels of the event hierarchy: events_stages_current for stage events, events_statements_current for statement events, and events_transactions_current for transaction events.

  • History tables. These tables have the same structure as the current events tables, but contain more rows. For example, for wait events, events_waits_history table contains the most recent 10 events per thread. events_waits_history_long contains the most recent 10,000 events. Other similar tables exist for stage, statement, and transaction histories.

    To change the sizes of the history tables, set the appropriate system variables at server startup. For example, to set the sizes of the wait event history tables, set performance_schema_events_waits_history_size and performance_schema_events_waits_history_long_size.

  • Summary tables. These tables contain information aggregated over groups of 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.


User Comments
Sign Up Login You must be logged in to post a comment.