Performance Schema Summary Tables the events on which wait summaries are based. See that discussion for information about the content of wait events, the current and recent wait event tables, and how to control wait event collection, which is disabled by default. Example wait event summary information: mysql>  SELECT * FROM performance_schema.events_waits_summary_global_by_event_name\G ... *************************** 6. row *************************** EVENT_NAME: wait/synch/mutex/sql/BINARY_LOG::LOCK_index COUNT_STAR: 8 SUM_TIMER_WAIT: 2119302 MIN_TIMER_WAIT: 196092 AVG_TIMER_WAIT: 264912 MAX_TIMER_WAIT: 569421 ... *************************** 9. row *************************** EVENT_NAME: wait/synch/mutex/sql/hash_filo::lock COUNT_STAR: 69 SUM_TIMER_WAIT: 16848828 MIN_TIMER_WAIT: 0 AVG_TIMER_WAIT: 244185 MAX_TIMER_WAIT: 735345 ... Each wait event summary table has one or more grouping columns to indicate how the table aggregates events. Event names refer to names of event instruments in the  setup_instruments  table: Each wait event summary table has these summary columns containing aggregated values: The number of summarized events. This value includes all events, whether timed or nontimed. • events_waits_summary_by_account_by_event_name  has  EVENT_NAME ,  USER , and  HOST columns. Each row summarizes events for a given account (user and host combination) and event name. • events_waits_summary_by_host_by_event_name  has  EVENT_NAME  and  HOST  columns. Each row summarizes events for a given host and event name. • events_waits_summary_by_instance  has  EVENT_NAME  and  OBJECT_INSTANCE_BEGIN columns. Each row summarizes events for a given event name and object. If an instrument is used to create multiple instances, each instance has a unique  OBJECT_INSTANCE_BEGIN  value and is summarized separately in this table. • events_waits_summary_by_thread_by_event_name  has  THREAD_ID  and  EVENT_NAME columns. Each row summarizes events for a given thread and event name. • events_waits_summary_by_user_by_event_name  has  EVENT_NAME  and  USER  columns. Each row summarizes events for a given user and event name. • events_waits_summary_global_by_event_name  has an  EVENT_NAME  column. Each row summarizes events for a given event name. An instrument might be used to create multiple instances of the instrumented object. For example, if there is an instrument for a mutex that is created for each connection, there are as many instances as there are connections. The summary row for the instrument summarizes over all these instances. • COUNT_STAR • SUM_TIMER_WAIT 5051