Performance Schema Quick Start | objects_summary_global_by_type | | performance_timers | | replication_connection_configuration | | replication_connection_status | | replication_applier_configuration | | replication_applier_status | | replication_applier_status_by_coordinator | | replication_applier_status_by_worker | | rwlock_instances | | session_account_connect_attrs | | session_connect_attrs | | setup_actors | | setup_consumers | | setup_instruments | | setup_objects | | socket_instances | | socket_summary_by_event_name | | socket_summary_by_instance | | table_handles | | table_io_waits_summary_by_index_usage | | table_io_waits_summary_by_table | | table_lock_waits_summary_by_table | | threads | | users | +------------------------------------------------------+ mysql>  SHOW TABLES FROM performance_schema; +------------------------------------------------------+ | Tables_in_performance_schema | +------------------------------------------------------+ | accounts | | cond_instances | | events_stages_current | | events_stages_history | | events_stages_history_long | ... The number of Performance Schema tables increases over time as implementation of additional instrumentation proceeds. The name of the  performance_schema  database is lowercase, as are the names of tables within it. Queries should specify the names in lowercase. To see the structure of individual tables, use  SHOW CREATE TABLE : mysql>  SHOW CREATE TABLE performance_schema.setup_consumers\G *************************** 1. row *************************** Table: setup_consumers Create Table: CREATE TABLE ‘setup_consumers‘ ( ‘NAME‘ varchar(64) NOT NULL, ‘ENABLED‘ enum(’YES’,’NO’) NOT NULL, PRIMARY KEY (‘NAME‘) ) ENGINE=PERFORMANCE_SCHEMA DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci Table structure is also available by selecting from tables such as  INFORMATION_SCHEMA.COLUMNS  or by using statements such as  SHOW COLUMNS . Tables in the  performance_schema  database can be grouped according to the type of information in them: Current events, event histories and summaries, object instances, and setup (configuration) information. The following examples illustrate a few uses for these tables. For detailed information about the tables in each group, see Section 27.12, “Performance Schema Table Descriptions” . Initially, not all instruments and consumers are enabled, so the performance schema does not collect all events. To turn all of these on and enable event timing, execute two statements (the row counts may differ depending on MySQL version): 4897