等待事件

最新推荐文章于 2023-07-13 23:51:43 发布

Snowballl

最新推荐文章于 2023-07-13 23:51:43 发布

阅读量478

点赞数

分类专栏： mysql

本文链接：https://blog.csdn.net/minwang593/article/details/115746960

版权

mysql 专栏收录该内容

36 篇文章 0 订阅

订阅专栏

第一章节等待事件

1.1performance_schema查看配置表如下

mysql> SELECT table_name

FROM information_schema.tables t

WHERE t.table_schema='performance_schema'

AND t.table_name LIKE 'setup%' ;

+-------------------+

| table_name |

+-------------------+

| setup_actors | --配置监控的范围

| setup_consumers | --配置监控的类型

| setup_instruments | --配置等待事件的类型

| setup_objects | --配置监控的对象

| setup_timers | --配置时间计量单位(皮秒)，8.0版本会被废除

+-------------------+

5 rows in set (0.00 sec)

1.2查看监控的范围，默认监控所有的host，所有的user

mysql> SELECT * FROM performance_schema.setup_actors;

+------+------+------+---------+---------+

+------+------+------+---------+---------+

| % | % | % | YES | YES |

+------+------+------+---------+---------+

1 row in set (0.00 sec)

The setup_actors table has these columns:

HOST：The host name. This should be a literal name, or '%' to mean “any host.”

USER：The user name. This should be a literal name, or '%' to mean “any user.”

ROLE：Unused.

ENABLED：Whether to enable instrumentation for foreground threads matched by the row. The value is YES or NO.

HISTORY：Whether to log historical events for foreground threads matched by the row. The value is YES or NO.

1.3查看当前监控的类型(写入到哪些监控的统计表里)和是否开启监控，默认开启如下

SELECT * FROM performance_schema.setup_consumers where enabled='YES'

mysql> SELECT * FROM performance_schema.setup_consumers;

+----------------------------------+---------+

| NAME | ENABLED |

+----------------------------------+---------+

| events_stages_current | NO |

| events_stages_history | NO |

| events_stages_history_long | NO |

| events_statements_current | YES |

| events_statements_history | YES |

| events_statements_history_long | NO |

| events_transactions_current | NO |

| events_transactions_history | NO |

| events_transactions_history_long | NO |

| events_waits_current | NO |

| events_waits_history | NO |

| events_waits_history_long | NO |

| global_instrumentation | YES |

| thread_instrumentation | YES |

| statements_digest | YES |

+----------------------------------+---------+

15 rows in set (0.00 sec)

1.4查看等待事件的类型和是否开启了这种类型的记录

--1022种类型，这里按等待类型查看数量

mysql> SELECT SUBSTRING_INDEX(NAME, '/', 1),COUNT(1)

FROM performance_schema.setup_instruments

GROUP BY 1

ORDER BY 2 DESC;

+-------------------------------+----------+

| SUBSTRING_INDEX(NAME, '/', 1) | COUNT(1) |

+-------------------------------+----------+

| memory | 377 |

| wait | 321 | --等待事件

| statement | 193 | --语句执行的信息

| stage | 129 | --语句执行阶段的时间统计

| idle | 1 | --空闲

| transaction | 1 |

+-------------------------------+----------+

6 rows in set (0.00 sec)

1.5查看监控的对象，默认对mysql、performance_schema、information_schema三个库的用户对象都不做监控

SELECT * FROM performance_schema.setup_objects where

OBJECT_schema not in ('mysql','performance_schema','information_schema')

mysql> SELECT * FROM performance_schema.setup_objects;

+-------------+--------------------+-------------+---------+-------+

+-------------+--------------------+-------------+---------+-------+

| EVENT | mysql | % | NO | NO |

| EVENT | performance_schema | % | NO | NO |

| EVENT | information_schema | % | NO | NO |

| EVENT | % | % | YES | YES |

| FUNCTION | mysql | % | NO | NO |

| FUNCTION | performance_schema | % | NO | NO |

| FUNCTION | information_schema | % | NO | NO |

| FUNCTION | % | % | YES | YES |

| PROCEDURE | mysql | % | NO | NO |

| PROCEDURE | performance_schema | % | NO | NO |

| PROCEDURE | information_schema | % | NO | NO |

| PROCEDURE | % | % | YES | YES |

| TABLE | mysql | % | NO | NO |

| TABLE | performance_schema | % | NO | NO |

| TABLE | information_schema | % | NO | NO |

| TABLE | % | % | YES | YES |

| TRIGGER | mysql | % | NO | NO |

| TRIGGER | performance_schema | % | NO | NO |

| TRIGGER | information_schema | % | NO | NO |

| TRIGGER | % | % | YES | YES |

+-------------+--------------------+-------------+---------+-------+

20 rows in set (0.00 sec)

1.6查看时间单位计量，都是皮秒(1秒＝1000000000000皮秒)，8.0版本废除的表

mysql> SELECT * FROM performance_schema.setup_timers;

+-------------+-------------+

| NAME | TIMER_NAME |

+-------------+-------------+

| idle | MICROSECOND |

| wait | CYCLE |

| stage | NANOSECOND |

| statement | NANOSECOND |

| transaction | NANOSECOND |

+-------------+-------------+

5 rows in set, 1 warning (0.00 sec)

记录执行语句的等待事件表，官方文档：https://dev.mysql.com/doc/refman/5.7/en/performance-schema-statement-tables.html

1.7查看可记录执行语句的等待事件的表，如下：

mysql> SELECT table_name

FROM information_schema.tables t

WHERE t.table_schema='performance_schema'

AND t.table_name LIKE 'events_statements%' ;

+----------------------------------------------------+

| table_name |

+----------------------------------------------------+

| events_statements_current |

| events_statements_history |

| events_statements_history_long |

| events_statements_summary_by_account_by_event_name |

| events_statements_summary_by_digest |

| events_statements_summary_by_host_by_event_name |

| events_statements_summary_by_program |

| events_statements_summary_by_thread_by_event_name |

| events_statements_summary_by_user_by_event_name |

| events_statements_summary_global_by_event_name |

+----------------------------------------------------+

10 rows in set (0.00 sec)

1.8查看是否开启了配置信息，写入到表中

mysql> SELECT *

FROM performance_schema.setup_consumers

WHERE NAME LIKE '%statements%';

+--------------------------------+---------+

| NAME | ENABLED |

+--------------------------------+---------+

| events_statements_current | YES |

| events_statements_history | YES |

| events_statements_history_long | NO |

| statements_digest | YES |

+--------------------------------+---------+

4 rows in set (0.00 sec)

mysql> SELECT *

FROM performance_schema.setup_instruments

WHERE NAME LIKE 'statement/%';

+---------------------------------------+---------+-------+

| NAME | ENABLED | TIMED |

+---------------------------------------+---------+-------+

| statement/sql/select | YES | YES |

| statement/sql/create_table | YES | YES |

| ......... |

| statement/abstract/new_packet | YES | YES |

| statement/abstract/relay_log | YES | YES |

+---------------------------------------+---------+-------+

193 rows in set (0.01 sec)

1.9可以在my.cnf配置，永久的开启配置信息来记录等待事件执行语句到表中

[mysqld]

performance-schema-instrument='statement/%=ON'

performance-schema-consumer-events-statements-current=ON

performance-schema-consumer-events-statements-history=ON

performance-schema-consumer-events-statements-history-long=ON

performance-schema-consumer-statements-digest=ON

--查看history历史表记录的数据量，history记录每个线程的最近10条，history_long记录所有线程的最近10000条

mysql> show variables like 'performance_schema_events_statements_history%';

+--------------------------------------------------------+-------+

| Variable_name | Value |

+--------------------------------------------------------+-------+

| performance_schema_events_statements_history_long_size | 10000 |

| performance_schema_events_statements_history_size | 10 |

+--------------------------------------------------------+-------+

2 rows in set (0.01 sec)

--查看历史执行时间最长的前5条sql记录，如下：

mysql> SELECT thread_id

,event_id

,event_name

,(timer_end-timer_start)/1000000000000 exec_time_sec

,lock_time/1000000000000 lock_time_sce

,SUBSTR(sql_text,1,50)

FROM performance_schema.events_statements_history

ORDER BY 4 DESC

LIMIT 5;

+-----------+----------+---------------------------+---------------+---------------+----------------------------------------------------+

+-----------+----------+---------------------------+---------------+---------------+----------------------------------------------------+

| 29 | 15305 | statement/sql/select | 0.0041 | 0.0037 | EXPLAIN select thread_id,event_id , |

| 29 | 15237 | statement/sql/show_status | 0.0018 | 0.0001 | SHOW STATUS |

| 29 | 15189 | statement/sql/show_status | 0.0016 | 0.0001 | SHOW STATUS |

| 32 | 341 | statement/sql/select | 0.0012 | 0.0001 | SELECT * FROM performance_schema.setup_inst |

| 32 | 397 | statement/sql/select | 0.0012 | 0.0002 | SELECT thread_id ,event_id ,event_na |

+-----------+----------+---------------------------+---------------+---------------+----------------------------------------------------+

5 rows in set (0.00 sec)

记录执行语句的等待事件表，官方文档：https://dev.mysql.com/doc/refman/5.7/en/performance-schema-stage-tables.html

1.10查看可记录语句每步执行时间的等待事件的表，如下：

mysql> SELECT table_name

FROM information_schema.tables t

WHERE t.table_schema='performance_schema'

AND t.table_name LIKE 'events_stages%';

+------------------------------------------------+

| table_name |

+------------------------------------------------+

| events_stages_current |

| events_stages_history |

| events_stages_history_long |

| events_stages_summary_by_account_by_event_name |

| events_stages_summary_by_host_by_event_name |

| events_stages_summary_by_thread_by_event_name |

| events_stages_summary_by_user_by_event_name |

| events_stages_summary_global_by_event_name |

+------------------------------------------------+

8 rows in set (0.00 sec)

1.11查看是否开启了配置信息，写入到表中

mysql> SELECT *

FROM performance_schema.setup_consumers

WHERE NAME LIKE '%stages%';

+----------------------------+---------+

| NAME | ENABLED |

+----------------------------+---------+

| events_stages_current | NO |

| events_stages_history | NO |

| events_stages_history_long | NO |

+----------------------------+---------+

3 rows in set (0.00 sec)

mysql> SELECT *

FROM performance_schema.setup_instruments

WHERE NAME LIKE 'stage%';

+----------------------------------------------------------------------------+---------+-------+

| NAME | ENABLED | TIMED |

+----------------------------------------------------------------------------+---------+-------+

| stage/sql/After create | NO | NO |

| stage/sql/allocating local table | NO | NO |

| stage/sql/preparing for alter table | NO | NO |

| stage/sql/altering table | NO | NO |

| stage/sql/committing alter table to storage engine | NO | NO |

| ......

| stage/innodb/buffer pool load | YES | YES |

+----------------------------------------------------------------------------+---------+-------+

129 rows in set (0.00 sec)

1.12可以在my.cnf配置，永久的开启配置信息来记录等待事件执行语句到表中

[mysqld]

performance-schema-instrument='stage/%=ON'

performance-schema-consumer-events-stages-current=ON

performance-schema-consumer-events-stages-history=ON

performance-schema-consumer-events-stages-history-long=ON

1.13查看history历史表记录的数据量，history记录每个线程的最近10条，history_long记录所有线程的最近10000条

mysql> show variables like 'performance_schema_events_stages_history%';

+----------------------------------------------------+-------+

| Variable_name | Value |

+----------------------------------------------------+-------+

| performance_schema_events_stages_history_long_size | 10000 |

| performance_schema_events_stages_history_size | 10 |

+----------------------------------------------------+-------+

2 rows in set (0.00 sec)

1.14查看历史执行时间最长的前5条每步具体时间，如下：

mysql> SELECT thread_id

,event_id

,event_name

,(timer_end-timer_start)/1000000000000 exec_time_sec

,timer_wait/1000000000000 timer_wait_sce

FROM performance_schema.events_stages_history

ORDER BY 4 DESC

LIMIT 5;

+-----------+----------+-------------------------------+---------------+----------------+

+-----------+----------+-------------------------------+---------------+----------------+

| 24 | 1 | stage/innodb/buffer pool load | 0.6036 | 0.6036 |

| 1 | 200 | stage/sql/System lock | 0.0081 | 0.0081 |

| 1 | 205 | stage/sql/Opening tables | 0.0029 | 0.0029 |

| 1 | 199 | stage/sql/Opening tables | 0.0005 | 0.0005 |

| 1 | 208 | stage/sql/System lock | 0.0003 | 0.0003 |

+-----------+----------+-------------------------------+---------------+----------------+

5 rows in set (0.00 sec)

记录执行语句的等待事件表，官方文档：https://dev.mysql.com/doc/refman/5.7/en/performance-schema-wait-tables.html

1.15查看可记录语句每步执行时间的等待事件的表，如下：

mysql> SELECT table_name

FROM information_schema.tables t

WHERE t.table_schema='performance_schema'

AND t.table_name LIKE 'events_waits%';

+-----------------------------------------------+

| table_name |

+-----------------------------------------------+

| events_waits_current |

| events_waits_history |

| events_waits_history_long |

| events_waits_summary_by_account_by_event_name |

| events_waits_summary_by_host_by_event_name |

| events_waits_summary_by_instance |

| events_waits_summary_by_thread_by_event_name |

| events_waits_summary_by_user_by_event_name |

| events_waits_summary_global_by_event_name |

+-----------------------------------------------+

9 rows in set (0.17 sec)

1.16查看是否开启了配置信息，写入到表中

mysql> SELECT *

FROM performance_schema.setup_consumers

WHERE NAME LIKE '%waits%';

+---------------------------+---------+

| NAME | ENABLED |

+---------------------------+---------+

| events_waits_current | NO |

| events_waits_history | NO |

| events_waits_history_long | NO |

+---------------------------+---------+

3 rows in set (0.04 sec)

mysql> SELECT *

FROM performance_schema.setup_instruments

WHERE NAME LIKE 'wait/%';

+--------------------------------------------------------------------+---------+-------+

| NAME | ENABLED | TIMED |

+--------------------------------------------------------------------+---------+-------+

| wait/synch/mutex/sql/TC_LOG_MMAP::LOCK_tc | NO | NO |

| wait/synch/mutex/sql/LOCK_des_key_file | NO | NO |

| wait/synch/mutex/sql/MYSQL_BIN_LOG::LOCK_commit | NO | NO |

| wait/synch/mutex/sql/MYSQL_BIN_LOG::LOCK_commit_queue | NO | NO |

| wait/synch/mutex/sql/MYSQL_BIN_LOG::LOCK_done | NO | NO |

......

| wait/lock/metadata/sql/mdl | NO | NO |

+--------------------------------------------------------------------+---------+-------+

321 rows in set (0.00 sec)

1.17可以在my.cnf配置，永久的开启配置信息来记录等待事件执行语句到表中

[mysqld]

performance-schema-instrument='stage/%=ON'

performance-schema-consumer-events-stages-current=ON

performance-schema-consumer-events-stages-history=ON

performance-schema-consumer-events-stages-history-long=ON

1.18查看history历史表记录的数据量，history记录每个线程的最近10条，history_long记录所有线程的最近10000条

mysql> show variables like 'performance_schema_events_waits_history%';

+---------------------------------------------------+-------+

| Variable_name | Value |

+---------------------------------------------------+-------+

| performance_schema_events_waits_history_long_size | 10000 |

| performance_schema_events_waits_history_size | 10 |

+---------------------------------------------------+-------+

2 rows in set (0.07 sec)

1.19查看历史执行时间最长的前5条每步具体时间，如下：

mysql> SELECT thread_id

,event_id

,event_name

,(timer_end-timer_start)/1000000000000 exec_time_sec

,timer_wait/1000000000000 timer_wait_sce

FROM performance_schema.events_waits_history

ORDER BY 4 DESC

LIMIT 5;

+-----------+----------+--------------------------------------------+---------------+----------------+

+-----------+----------+--------------------------------------------+---------------+----------------+

| 12 | 3 | wait/io/file/innodb/innodb_log_file | 0.0169 | 0.0169 |

| 6 | 113 | wait/io/file/innodb/innodb_data_file | 0.0169 | 0.0169 |

| 12 | 8 | wait/io/file/innodb/innodb_log_file | 0.0034 | 0.0034 |

| 30 | 1242 | wait/io/socket/sql/client_connection | 0.0001 | 0.0001 |

| 1 | 17170 | wait/synch/mutex/sql/LOCK_connection_count | 0.0000 | 0.0000 |

+-----------+----------+--------------------------------------------+---------------+----------------+

5 rows in set (0.00 sec)

1.20查看sql相应的具体等待事件

--执行一条测试的sql，分析此条sql的等待事件

mysql> SELECT /*+test_waits*/COUNT(1) FROM information_schema.columns;

+----------+

| COUNT(1) |

+----------+

| 3193 |

+----------+

1 row in set, 1 warning (0.08 sec)

1.21查看上述sql的每个阶段的时间和事件

--说明：events_statements*表的event_id字段和events_stages*表的nesting_event_id字段关联

mysql> SELECT statement.sql_text,

stages.event_id stage_event_id,

stages.event_name stage_event_name ,

stages.timer_wait/1000000000000 stage_timer_wait_sec --秒

FROM performance_schema.events_statements_history_long statement

JOIN performance_schema.events_stages_history_long stages

ON statement.event_id=stages.nesting_event_id

WHERE statement.sql_text LIKE 'SELECT /*+test_waits*/COUNT(1) FROM information_schema.columns'

ORDER BY stages.timer_wait DESC

LIMIT 10;

+----------------------------------------------------------------+----------------+--------------------------------+----------------------+

+----------------------------------------------------------------+----------------+--------------------------------+----------------------+

| SELECT /*+test_waits*/COUNT(1) FROM information_schema.columns | 59168 | stage/sql/checking permissions | 0.0064 |

| SELECT /*+test_waits*/COUNT(1) FROM information_schema.columns | 69109 | stage/sql/Sending data | 0.0052 |

| SELECT /*+test_waits*/COUNT(1) FROM information_schema.columns | 56443 | stage/sql/checking permissions | 0.0032 |

| SELECT /*+test_waits*/COUNT(1) FROM information_schema.columns | 57885 | stage/sql/Opening tables | 0.0015 |

| SELECT /*+test_waits*/COUNT(1) FROM information_schema.columns | 56371 | stage/sql/starting | 0.0012 |

| SELECT /*+test_waits*/COUNT(1) FROM information_schema.columns | 65769 | stage/sql/Opening tables | 0.0012 |

| SELECT /*+test_waits*/COUNT(1) FROM information_schema.columns | 65969 | stage/sql/Opening tables | 0.0006 |

| SELECT /*+test_waits*/COUNT(1) FROM information_schema.columns | 58929 | stage/sql/checking permissions | 0.0006 |

| SELECT /*+test_waits*/COUNT(1) FROM information_schema.columns | 68261 | stage/sql/Opening tables | 0.0005 |

| SELECT /*+test_waits*/COUNT(1) FROM information_schema.columns | 66097 | stage/sql/Opening tables | 0.0004 |

+----------------------------------------------------------------+----------------+--------------------------------+----------------------+

10 rows in set (0.08 sec)

1.22查看上述第二行的阶段(红色)的具体等待事件，如下：

--说明：events_stages*表的event_id字段和events_waits*表的nesting_event_id字段关联

mysql> SELECT thread_id

,event_id

,event_name

,(timer_end-timer_start) exec_time --皮秒

,timer_wait timer_wait --皮秒

FROM performance_schema.events_waits_history_long t

WHERE t.nesting_event_id = 69109

ORDER BY timer_wait DESC;

+-----------+----------+-------------------------------------------+-----------+------------+

+-----------+----------+-------------------------------------------+-----------+------------+

| 29 | 69112 | wait/synch/sxlock/innodb/hash_table_locks | 626410 | 626410 |

| 29 | 69115 | wait/synch/sxlock/innodb/hash_table_locks | 194250 | 194250 |

| 29 | 69114 | wait/synch/sxlock/innodb/hash_table_locks | 156880 | 156880 |

| 29 | 69121 | wait/synch/sxlock/innodb/hash_table_locks | 150960 | 150960 |

| 29 | 69119 | wait/synch/sxlock/innodb/hash_table_locks | 145040 | 145040 |

| 29 | 69116 | wait/synch/sxlock/innodb/hash_table_locks | 125430 | 125430 |

| 29 | 69123 | wait/synch/sxlock/innodb/hash_table_locks | 122100 | 122100 |

| 29 | 69117 | wait/synch/sxlock/innodb/hash_table_locks | 121360 | 121360 |

| 29 | 69113 | wait/synch/sxlock/innodb/hash_table_locks | 119880 | 119880 |

| 29 | 69122 | wait/synch/sxlock/innodb/hash_table_locks | 119510 | 119510 |

| 29 | 69120 | wait/synch/sxlock/innodb/hash_table_locks | 115810 | 115810 |

| 29 | 69118 | wait/synch/sxlock/innodb/hash_table_locks | 110630 | 110630 |

| 29 | 69133 | wait/synch/sxlock/innodb/hash_table_locks | 106930 | 106930 |

| 29 | 69140 | wait/synch/sxlock/innodb/hash_table_locks | 106190 | 106190 |

| 29 | 69126 | wait/synch/sxlock/innodb/hash_table_locks | 105450 | 105450 |

| 29 | 69147 | wait/synch/sxlock/innodb/hash_table_locks | 96570 | 96570 |

| 29 | 69110 | wait/synch/mutex/innodb/trx_mutex | 90280 | 90280 |

| 29 | 69124 | wait/synch/sxlock/innodb/hash_table_locks | 68080 | 68080 |

| 29 | 69127 | wait/synch/sxlock/innodb/hash_table_locks | 66600 | 66600 |

| 29 | 69144 | wait/synch/sxlock/innodb/hash_table_locks | 65860 | 65860 |

| 29 | 69143 | wait/synch/sxlock/innodb/hash_table_locks | 64750 | 64750 |

| 29 | 69141 | wait/synch/sxlock/innodb/hash_table_locks | 64010 | 64010 |

| 29 | 69132 | wait/synch/sxlock/innodb/hash_table_locks | 63270 | 63270 |

| 29 | 69142 | wait/synch/sxlock/innodb/hash_table_locks | 61050 | 61050 |

| 29 | 69137 | wait/synch/sxlock/innodb/hash_table_locks | 60680 | 60680 |

| 29 | 69145 | wait/synch/sxlock/innodb/hash_table_locks | 60310 | 60310 |

| 29 | 69146 | wait/synch/sxlock/innodb/hash_table_locks | 59940 | 59940 |

| 29 | 69128 | wait/synch/sxlock/innodb/hash_table_locks | 59570 | 59570 |

| 29 | 69134 | wait/synch/sxlock/innodb/hash_table_locks | 58830 | 58830 |

| 29 | 69131 | wait/synch/sxlock/innodb/hash_table_locks | 58830 | 58830 |

| 29 | 69125 | wait/synch/sxlock/innodb/hash_table_locks | 58460 | 58460 |

| 29 | 69129 | wait/synch/sxlock/innodb/hash_table_locks | 58090 | 58090 |

| 29 | 69136 | wait/synch/sxlock/innodb/hash_table_locks | 57350 | 57350 |

| 29 | 69135 | wait/synch/sxlock/innodb/hash_table_locks | 56240 | 56240 |

| 29 | 69139 | wait/synch/sxlock/innodb/hash_table_locks | 55500 | 55500 |

| 29 | 69138 | wait/synch/sxlock/innodb/hash_table_locks | 55130 | 55130 |

| 29 | 69130 | wait/synch/sxlock/innodb/hash_table_locks | 52910 | 52910 |

| 29 | 69111 | wait/synch/mutex/innodb/trx_mutex | 36630 | 36630 |

第二章节 performance_schema简介

参照：

https://blog.csdn.net/qq_35068291/article/details/105921515

2.1特点

1、提供了一种在数据库运行时实时检查server的内部执行情况的方法。performance_schema 数据库中的表使用performance_schema存储引擎。该数据库主要关注数据库运行过程中的性能相关的数据，与information_schema不同，information_schema主要关注server运行过程中的元数据信息。

2、performance_schema通过监视server的事件来实现监视server内部运行情况， “事件”就是server内部活动中所做的任何事情以及对应的时间消耗，利用这些信息来判断server中的相关资源消耗在了哪里？一般来说，事件可以是函数调用、操作系统的等待、SQL语句执行的阶段（如sql语句执行过程中的parsing 或 sorting阶段）或者整个SQL语句与SQL语句集合。事件的采集可以方便的提供server中的相关存储引擎对磁盘文件、表I/O、表锁等资源的同步调用信息。

3、performance_schema中的事件与写入二进制日志中的事件（描述数据修改的events）、事件计划调度程序（这是一种存储程序）的事件不同。performance_schema中的事件记录的是server执行某些活动对某些资源的消耗、耗时、这些活动执行的次数等情况。

4、performance_schema中的事件只记录在本地server的performance_schema中，其下的这些表中数据发生变化时不会被写入binlog中，也不会通过复制机制被复制到其他server中。

5、当前活跃事件、历史事件和事件摘要相关的表中记录的信息。能提供某个事件的执行次数、使用时长。进而可用于分析某个特定线程、特定对象（如mutex或file）相关联的活动。

6、PERFORMANCE_SCHEMA存储引擎使用server源代码中的“检测点”来实现事件数据的收集。对于performance_schema实现机制本身的代码没有相关的单独线程来检测，这与其他功能（如复制或事件计划程序）不同。

7、收集的事件数据存储在performance_schema数据库的表中。这些表可以使用SELECT语句查询，也可以使用SQL语句更新performance_schema数据库中的表记录（如动态修改performance_schema的setup_*开头的几个配置表，但要注意：配置表的更改会立即生效，这会影响数据收集）

8、performance_schema的表中的数据不会持久化存储在磁盘中，而是保存在内存中，一旦服务器重启，这些数据会丢失（包括配置表在内的整个performance_schema下的所有数据）

9、MySQL支持的所有平台中事件监控功能都可用，但不同平台中用于统计事件时间开销的计时器类型可能会有所差异。

2.2操作

在mysql的5.7版本中，性能模式是默认开启的，如果想要显式的关闭的话需要修改配置文件，不能直接进行修改，会报错Variable ‘performance_schema’ is a read only variable

2.2.1查看performance_schema的属性

MySQL [juncdt_dw]> SHOW VARIABLES LIKE 'performance_schema';

+--------------------+-------+

| Variable_name | Value |

+--------------------+-------+

| performance_schema | ON |

+--------------------+-------+

1 row in set (0.00 sec)

2.2.2查看setup_consumers--消费者

想要搞明白后续的内容，同学们需要理解两个基本概念：

instruments: 生产者，用于采集mysql中各种各样的操作产生的事件信息，对应配置表中的配置项我们可以称为监控采集配置项。

consumers:消费者，对应的消费者表用于存储来自instruments采集的数据，对应配置表中的配置项我们可以称为消费存储配置项。

MySQL [performance_schema]> show create table setup_consumers;

+-----------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

| Table | Create Table |

| setup_consumers | 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 |

1 row in set (0.00 sec)

MySQL [performance_schema]> select * from setup_consumers;

+----------------------------------+---------+

| NAME | ENABLED |

+----------------------------------+---------+

| events_stages_current | NO |

| events_stages_history | NO |

| events_stages_history_long | NO |

| events_statements_current | YES |

| events_statements_history | YES |

| events_statements_history_long | NO |

| events_transactions_current | YES |

| events_transactions_history | YES |

| events_transactions_history_long | NO |

| events_waits_current | NO |

| events_waits_history | NO |

| events_waits_history_long | NO |

| global_instrumentation | YES |

| thread_instrumentation | YES |

| statements_digest | YES |

+----------------------------------+---------+

15 rows in set (0.00 sec)

2.3performance_schema表的分类

2.3.1语句事件表

语句事件记录表，这些表记录了语句事件信息，当前语句事件表events_statements_current、历史语句事件表events_statements_history和长语句历史事件表events_statements_history_long、以及聚合后的摘要表summary，其中，summary表还可以根据帐号(account)，主机(host)，程序(program)，线程(thread)，用户(user)和全局(global)再进行细分)

MySQL [performance_schema]> show tables like '%statement%';

+----------------------------------------------------+

| Tables_in_performance_schema (%statement%) |

+----------------------------------------------------+

| events_statements_current |

| events_statements_histogram_by_digest |

| events_statements_histogram_global |

| events_statements_history |

| events_statements_history_long |

| events_statements_summary_by_account_by_event_name |

| events_statements_summary_by_digest |

| events_statements_summary_by_host_by_event_name |

| events_statements_summary_by_program |

| events_statements_summary_by_thread_by_event_name |

| events_statements_summary_by_user_by_event_name |

| events_statements_summary_global_by_event_name |

| prepared_statements_instances |

+----------------------------------------------------+

13 rows in set (0.04 sec)

2.3.2等待事件记录表，与语句事件类型的相关记录表类似

MySQL [performance_schema]> show tables like '%wait%';

+-----------------------------------------------+

| Tables_in_performance_schema (%wait%) |

+-----------------------------------------------+

| data_lock_waits |

| events_waits_current |

| events_waits_history |

| events_waits_history_long |

| events_waits_summary_by_account_by_event_name |

| events_waits_summary_by_host_by_event_name |

| events_waits_summary_by_instance |

| events_waits_summary_by_thread_by_event_name |

| events_waits_summary_by_user_by_event_name |

| events_waits_summary_global_by_event_name |

| table_io_waits_summary_by_index_usage |

| table_io_waits_summary_by_table |

| table_lock_waits_summary_by_table |

+-----------------------------------------------+

概而论数据库

select object_type as 对象类型,object_schema as 数据库, OBJECT_NAME as 对象名, sum_timer_wait as 总的等待时间 from performance_schema.table_lock_waits_summary_by_table

order by sum_timer_wait

desc

注：可以看出这些表操作特别的频繁，可以考虑进行处理

2.3.3 阶段事件记录表，记录语句执行的阶段事件的表

MySQL [performance_schema]> show tables like '%stage%';

+------------------------------------------------+

| Tables_in_performance_schema (%stage%) |

+------------------------------------------------+

| events_stages_current |

| events_stages_history |

| events_stages_history_long |

| events_stages_summary_by_account_by_event_name |

| events_stages_summary_by_host_by_event_name |

| events_stages_summary_by_thread_by_event_name |

| events_stages_summary_by_user_by_event_name |

| events_stages_summary_global_by_event_name |

+------------------------------------------------+

8 rows in set (0.00 sec)

2.3.4 事务事件记录表，记录事务相关的事件的表

MySQL [performance_schema]> show tables like '%transaction%';

+------------------------------------------------------+

| Tables_in_performance_schema (%transaction%) |

+------------------------------------------------------+

| binary_log_transaction_compression_stats |

| events_transactions_current |

| events_transactions_history |

| events_transactions_history_long |

| events_transactions_summary_by_account_by_event_name |

| events_transactions_summary_by_host_by_event_name |

| events_transactions_summary_by_thread_by_event_name |

| events_transactions_summary_by_user_by_event_name |

| events_transactions_summary_global_by_event_name |

+------------------------------------------------------+

9 rows in set (0.00 sec)

2.3.5监控文件系统层调用的表

MySQL [performance_schema]> show tables like '%file%';

+---------------------------------------+

| Tables_in_performance_schema (%file%) |

+---------------------------------------+

| file_instances |

| file_summary_by_event_name |

| file_summary_by_instance |

+---------------------------------------+

3 rows in set (0.01 sec)

2.3.6监控文件系统层调用的表

MySQL [performance_schema]> show tables like '%memory%';

+-----------------------------------------+

| Tables_in_performance_schema (%memory%) |

+-----------------------------------------+

| memory_summary_by_account_by_event_name |

| memory_summary_by_host_by_event_name |

| memory_summary_by_thread_by_event_name |

| memory_summary_by_user_by_event_name |

| memory_summary_global_by_event_name |

+-----------------------------------------+

5 rows in set (0.00 sec)

2.3.7动态对performance_schema进行配置的配置表

MySQL [performance_schema]> show tables like '%setup%';

+----------------------------------------+

| Tables_in_performance_schema (%setup%) |

+----------------------------------------+

| setup_actors |

| setup_consumers |

| setup_instruments |

| setup_objects |

| setup_threads |

+----------------------------------------+

5 rows in set (0.00 sec)

2.4performance_schema的简单配置与使用

数据库刚刚初始化并启动时，并非所有instruments(事件采集项，在采集项的配置表中每一项都有一个开关字段，或为YES，或为NO)和consumers(与采集项类似，也有一个对应的事件类型保存表配置项，为YES就表示对应的表保存性能数据，为NO就表示对应的表不保存性能数据)都启用了，所以默认不会收集所有的事件，可能你需要检测的事件并没有打开，需要进行设置，可以使用如下两个语句打开对应的instruments和consumers（行计数可能会因MySQL版本而异)。

--打开等待事件的采集器配置项开关，需要修改setup_instruments配置表中对应的采集器配置项

UPDATE setup_instruments SET ENABLED = 'YES', TIMED = 'YES'where name like 'wait%';

--打开等待事件的保存表配置开关，修改setup_consumers配置表中对应的配置项

UPDATE setup_consumers SET ENABLED = 'YES'where name like '%wait%';

--当配置完成之后可以查看当前server正在做什么，可以通过查询events_waits_current表来得知，该表中每个线程只包含一行数据，用于显示每个线程的最新监视事件

select * from events_waits_current\G

*************************** 1. row ***************************

THREAD_ID: 11

EVENT_ID: 570

END_EVENT_ID: 570

EVENT_NAME: wait/synch/mutex/innodb/buf_dblwr_mutex

SOURCE:

TIMER_START: 4508505105239280

TIMER_END: 4508505105270160

TIMER_WAIT: 30880

SPINS: NULL

OBJECT_SCHEMA: NULL

OBJECT_NAME: NULL

INDEX_NAME: NULL

OBJECT_TYPE: NULL

OBJECT_INSTANCE_BEGIN: 67918392

NESTING_EVENT_ID: NULL

NESTING_EVENT_TYPE: NULL

OPERATION: lock

NUMBER_OF_BYTES: NULL

FLAGS: NULL

/*该信息表示线程id为11的线程正在等待buf_dblwr_mutex锁，等待事件为30880

属性说明：

id:事件来自哪个线程，事件编号是多少

event_name:表示检测到的具体的内容

source:表示这个检测代码在哪个源文件中以及行号

timer_start:表示该事件的开始时间

timer_end:表示该事件的结束时间

timer_wait:表示该事件总的花费时间

注意：_current表中每个线程只保留一条记录，一旦线程完成工作，该表中不会再记录该线程的事件信息

_history表中记录每个线程应该执行完成的事件信息，但每个线程的事件信息只会记录10条，再多就会被覆盖，*_history_long表中记录所有线程的事件信息，但总记录数量是10000，超过就会被覆盖掉

select thread_id,event_id,event_name,timer_wait from events_waits_history order by thread_id limit 21;

summary表提供所有事件的汇总信息，该组中的表以不同的方式汇总事件数据（如：按用户，按主机，按线程等等）。例如：要查看哪些instruments占用最多的时间，可以通过对events_waits_summary_global_by_event_name表的COUNT_STAR或SUM_TIMER_WAIT列进行查询（这两列是对事件的记录数执行COUNT（*）、事件记录的TIMER_WAIT列执行SUM（TIMER_WAIT）统计而来）

SELECT EVENT_NAME,COUNT_STAR FROM events_waits_summary_global_by_event_name ORDER BY COUNT_STAR DESC LIMIT 10;

instance表记录了哪些类型的对象会被检测。这些对象在被server使用时，在该表中将会产生一条事件记录，例如，file_instances表列出了文件I/O操作及其关联文件名

select * from file_instances limit 20;

2.5常用配置向说明

performance_schema_consumer_events_statements_current=TRUE

是否在mysql server启动时就开启events_statements_current表的记录功能(该表记录当前的语句事件信息)，启动之后也可以在setup_consumers表中使用UPDATE语句进行动态更新setup_consumers配置表中的events_statements_current配置项，默认值为TRUE

performance_schema_consumer_events_statements_history=TRUE

与performance_schema_consumer_events_statements_current选项类似，但该选项是用于配置是否记录语句事件短历史信息，默认为TRUE

performance_schema_consumer_events_stages_history_long=FALSE

与performance_schema_consumer_events_statements_current选项类似，但该选项是用于配置是否记录语句事件长历史信息，默认为FALSE

除了statement(语句)事件之外，还支持：wait(等待)事件、state(阶段)事件、transaction(事务)事件，他们与statement事件一样都有三个启动项分别进行配置，但这些等待事件默认未启用，如果需要在MySQL Server启动时一同启动，则通常需要写进my.cnf配置文件中

performance_schema_consumer_global_instrumentation=TRUE

是否在MySQL Server启动时就开启全局表（如：mutex_instances、rwlock_instances、cond_instances、file_instances、users、hostsaccounts、socket_summary_by_event_name、file_summary_by_instance等大部分的全局对象计数统计和事件汇总统计信息表）的记录功能，启动之后也可以在setup_consumers表中使用UPDATE语句进行动态更新全局配置项

默认值为TRUE

performance_schema_consumer_statements_digest=TRUE

是否在MySQL Server启动时就开启events_statements_summary_by_digest 表的记录功能，启动之后也可以在setup_consumers表中使用UPDATE语句进行动态更新digest配置项

默认值为TRUE

performance_schema_consumer_thread_instrumentation=TRUE

是否在MySQL Server启动时就开启

events_xxx_summary_by_yyy_by_event_name表的记录功能，启动之后也可以在setup_consumers表中使用UPDATE语句进行动态更新线程配置项

默认值为TRUE

performance_schema_instrument[=name]

是否在MySQL Server启动时就启用某些采集器，由于instruments配置项多达数千个，所以该配置项支持key-value模式，还支持%号进行通配等，如下:

# [=name]可以指定为具体的Instruments名称（但是这样如果有多个需要指定的时候，就需要使用该选项多次），也可以使用通配符，可以指定instruments相同的前缀+通配符，也可以使用%代表所有的instruments

## 指定开启单个instruments

--performance-schema-instrument= 'instrument_name=value'

## 使用通配符指定开启多个instruments

--performance-schema-instrument= 'wait/synch/cond/%=COUNTED'

## 开关所有的instruments

--performance-schema-instrument= '%=ON'

--performance-schema-instrument= '%=OFF'

2.6系统变量

show variables like '%performance_schema%';

--重要的属性解释

一、performance_schema=ON

控制performance_schema功能的开关，要使用MySQL的performance_schema，需要在mysqld启动时启用，以启用事件收集功能

该参数在5.7.x之前支持performance_schema的版本中默认关闭，5.7.x版本开始默认开启

注意：如果mysqld在初始化performance_schema时发现无法分配任何相关的内部缓冲区，则performance_schema将自动禁用，并将performance_schema设置为OFF

二、performance_schema_digests_size=10000

控制events_statements_summary_by_digest表中的最大行数。如果产生的语句摘要信息超过此最大值，便无法继续存入该表，此时performance_schema会增加状态变量

三、performance_schema_events_statements_history_long_size=10000

控制events_statements_history_long表中的最大行数，该参数控制所有会话在events_statements_history_long表中能够存放的总事件记录数，超过这个限制之后，最早的记录将被覆盖

全局变量，只读变量，整型值，5.6.3版本引入 * 5.6.x版本中，5.6.5及其之前的版本默认为10000，5.6.6及其之后的版本默认值为-1，通常情况下，自动计算的值都是10000 * 5.7.x版本中，默认值为-1，通常情况下，自动计算的值都是10000

四、performance_schema_events_statements_history_size=10

控制events_statements_history表中单个线程（会话）的最大行数，该参数控制单个会话在events_statements_history表中能够存放的事件记录数，超过这个限制之后，单个会话最早的记录将被覆盖

全局变量，只读变量，整型值，5.6.3版本引入 * 5.6.x版本中，5.6.5及其之前的版本默认为10，5.6.6及其之后的版本默认值为-1，通常情况下，自动计算的值都是10 * 5.7.x版本中，默认值为-1，通常情况下，自动计算的值都是10

除了statement(语句)事件之外，wait(等待)事件、state(阶段)事件、transaction(事务)事件，他们与statement事件一样都有三个参数分别进行存储限制配置，有兴趣的同学自行研究，这里不再赘述

五、performance_schema_max_digest_length=1024

用于控制标准化形式的SQL语句文本在存入performance_schema时的限制长度，该变量与max_digest_length变量相关(max_digest_length变量含义请自行查阅相关资料)

全局变量，只读变量，默认值1024字节，整型值，取值范围0~1048576

六、performance_schema_max_sql_text_length=1024

控制存入events_statements_current，events_statements_history和events_statements_history_long语句事件表中的SQL_TEXT列的最大SQL长度字节数。超出系统变量performance_schema_max_sql_text_length的部分将被丢弃，不会记录，一般情况下不需要调整该参数，除非被截断的部分与其他SQL比起来有很大差异

全局变量，只读变量，整型值，默认值为1024字节，取值范围为0~1048576，5.7.6版本引入

降低系统变量performance_schema_max_sql_text_length值可以减少内存使用，但如果汇总的SQL中，被截断部分有较大差异，会导致没有办法再对这些有较大差异的SQL进行区分。增加该系统变量值会增加内存使用，但对于汇总SQL来讲可以更精准地区分不同的部分。

2.7重要配置表的相关说明

配置表之间存在相互关联关系，按照配置影响的先后顺序，可添加为

performance_timers表中记录了server中有哪些可用的事件计时器

字段解释：

timer_name:表示可用计时器名称，CYCLE是基于CPU周期计数器的定时器

timer_frequency:表示每秒钟对应的计时器单位的数量,CYCLE计时器的换算值与CPU的频率相关、

timer_resolution:计时器精度值，表示在每个计时器被调用时额外增加的值

timer_overhead:表示在使用定时器获取事件时开销的最小周期值

select * from performance_timers;

setup_timers表中记录当前使用的事件计时器信息

字段解释：

name:计时器类型，对应某个事件类别

timer_name:计时器类型名称

select * from setup_timers;

setup_consumers表中列出了consumers可配置列表项

字段解释：

NAME：consumers配置名称

ENABLED：consumers是否启用，有效值为YES或NO，此列可以使用UPDATE语句修改。

select * from setup_consumers;

setup_instruments 表列出了instruments 列表配置项，即代表了哪些事件支持被收集：

字段解释：

NAME：instruments名称，instruments名称可能具有多个部分并形成层次结构

ENABLED：instrumetns是否启用，有效值为YES或NO，此列可以使用UPDATE语句修改。如果设置为NO，则这个instruments不会被执行，不会产生任何的事件信息

TIMED：instruments是否收集时间信息，有效值为YES或NO，此列可以使用UPDATE语句修改，如果设置为NO，则这个instruments不会收集时间信息

SELECT * FROM setup_instruments;

setup_actors表的初始内容是匹配任何用户和主机，因此对于所有前台线程，默认情况下启用监视和历史事件收集功能

字段解释：

HOST：与grant语句类似的主机名，一个具体的字符串名字，或使用“％”表示“任何主机”

USER：一个具体的字符串名称，或使用“％”表示“任何用户”

ROLE：当前未使用，MySQL 8.0中才启用角色功能

ENABLED：是否启用与HOST，USER，ROLE匹配的前台线程的监控功能，有效值为：YES或NO

HISTORY：是否启用与HOST， USER，ROLE匹配的前台线程的历史事件记录功能，有效值为：YES或NO

SELECT * FROM setup_actors;

setup_objects表控制performance_schema是否监视特定对象。默认情况下，此表的最大行数为100行。

字段解释：

OBJECT_TYPE：instruments类型，有效值为：“EVENT”（事件调度器事件）、“FUNCTION”（存储函数）、“PROCEDURE”（存储过程）、“TABLE”（基表）、“TRIGGER”（触发器），TABLE对象类型的配置会影响表I/O事件（wait/io/table/sql/handler instrument）和表锁事件（wait/lock/table/sql/handler instrument）的收集

OBJECT_SCHEMA：某个监视类型对象涵盖的数据库名称，一个字符串名称，或“％”(表示“任何数据库”)

OBJECT_NAME：某个监视类型对象涵盖的表名，一个字符串名称，或“％”(表示“任何数据库内的对象”)

ENABLED：是否开启对某个类型对象的监视功能，有效值为：YES或NO。此列可以修改

TIMED：是否开启对某个类型对象的时间收集功能，有效值为：YES或NO，此列可以修改

SELECT * FROM setup_objects;

threads表对于每个server线程生成一行包含线程相关的信息，

字段解释：

THREAD_ID：线程的唯一标识符（ID）

NAME：与server中的线程检测代码相关联的名称(注意，这里不是instruments名称)

TYPE：线程类型，有效值为：FOREGROUND、BACKGROUND。分别表示前台线程和后台线程

PROCESSLIST_ID：对应INFORMATION_SCHEMA.PROCESSLIST表中的ID列。

PROCESSLIST_USER：与前台线程相关联的用户名，对于后台线程为NULL。

PROCESSLIST_HOST：与前台线程关联的客户端的主机名，对于后台线程为NULL。

PROCESSLIST_DB：线程的默认数据库，如果没有，则为NULL。

PROCESSLIST_COMMAND：对于前台线程，该值代表着当前客户端正在执行的command类型，如果是sleep则表示当前会话处于空闲状态

PROCESSLIST_TIME：当前线程已处于当前线程状态的持续时间（秒）

PROCESSLIST_STATE：表示线程正在做什么事情。

PROCESSLIST_INFO：线程正在执行的语句，如果没有执行任何语句，则为NULL。

PARENT_THREAD_ID：如果这个线程是一个子线程（由另一个线程生成），那么该字段显示其父线程ID

ROLE：暂未使用

INSTRUMENTED：线程执行的事件是否被检测。有效值：YES、NO

HISTORY：是否记录线程的历史事件。有效值：YES、NO *

THREAD_OS_ID：由操作系统层定义的线程或任务标识符（ID）：

select * from threads

2.8performance_schema实践操作

2.8.1哪类的SQL执行最多？

SELECT DIGEST_TEXT,COUNT_STAR,FIRST_SEEN,LAST_SEEN FROM events_statements_summary_by_digest ORDER BY COUNT_STAR DESC

2.8.2哪类SQL的平均响应时间最多？

SELECT DIGEST_TEXT,AVG_TIMER_WAIT FROM events_statements_summary_by_digest ORDER BY COUNT_STAR DESC

2.8.3哪类SQL排序记录数最多？

SELECT DIGEST_TEXT,SUM_SORT_ROWS FROM events_statements_summary_by_digest ORDER BY COUNT_STAR DESC

2.8.4哪类SQL扫描记录数最多？

SELECT DIGEST_TEXT,SUM_ROWS_EXAMINED FROM events_statements_summary_by_digest ORDER BY COUNT_STAR DESC

2.8.5哪类SQL使用临时表最多？

SELECT DIGEST_TEXT,SUM_CREATED_TMP_TABLES,SUM_CREATED_TMP_DISK_TABLES FROM events_statements_summary_by_digest ORDER BY COUNT_STAR DESC

2.8.6哪类SQL返回结果集最多？

SELECT DIGEST_TEXT,SUM_ROWS_SENT FROM events_statements_summary_by_digest ORDER BY COUNT_STAR DESC

2.8.7哪个表物理IO最多？

SELECT file_name,event_name,SUM_NUMBER_OF_BYTES_READ,SUM_NUMBER_OF_BYTES_WRITE FROM file_summary_by_instance ORDER BY SUM_NUMBER_OF_BYTES_READ + SUM_NUMBER_OF_BYTES_WRITE DESC

2.8.8哪个表逻辑IO最多？

SELECT object_name,COUNT_READ,COUNT_WRITE,COUNT_FETCH,SUM_TIMER_WAIT FROM table_io_waits_summary_by_table ORDER BY sum_timer_wait DESC

2.8.9哪个索引访问最多？

SELECT OBJECT_NAME,INDEX_NAME,COUNT_FETCH,COUNT_INSERT,COUNT_UPDATE,COUNT_DELETE FROM table_io_waits_summary_by_index_usage ORDER BY SUM_TIMER_WAIT DESC

2.8.10哪个索引从来没有用过？

SELECT OBJECT_SCHEMA,OBJECT_NAME,INDEX_NAME FROM table_io_waits_summary_by_index_usage WHERE INDEX_NAME IS NOT NULL AND COUNT_STAR = 0 AND OBJECT_SCHEMA <> 'mysql' ORDER BY OBJECT_SCHEMA,OBJECT_NAME;

2.8.12哪个等待事件消耗时间最多？

SELECT EVENT_NAME,COUNT_STAR,SUM_TIMER_WAIT,AVG_TIMER_WAIT FROM events_waits_summary_global_by_event_name WHERE event_name != 'idle' ORDER BY SUM_TIMER_WAIT DESC

2.8.13剖析某条SQL的执行情况，包括statement信息，stege信息，wait信息

SELECT EVENT_ID,sql_text FROM events_statements_history WHERE sql_text LIKE '%count(*)%';

2.8.14查看每个阶段的时间消耗

SELECT event_id,EVENT_NAME,SOURCE,TIMER_END - TIMER_START FROM events_stages_history_long WHERE NESTING_EVENT_ID = 1553;

2.8.15查看每个阶段的锁等待情况

SELECT event_id,event_name,source,timer_wait,object_name,index_name,operation,nesting_event_id FROM events_waits_history_long WHERE nesting_event_id = 1553;

2.8.16总结

主要特别重要的性能表(这几张表)：

events_statements_summary_by_digest、

file_summary_by_instance、

table_io_waits_summary_by_table、

table_io_waits_summary_by_index_usage、

events_statements_history、events_waits_history_long

Snowballl

关注

0
点赞
踩
1

收藏

觉得还不错? 一键收藏
0
评论
等待事件

第一章节等待事件1.1performance_schema查看配置表如下mysql> SELECT table_nameFROM information_schema.tables tWHERE t.table_schema='performance_schema'AND t.table_name LIKE 'setup%' ;+-------------------+| table_na...
复制链接

扫一扫