📋 目录一、统计概览二、Top10 明细三、高频慢查询模式(SQL 指纹聚合)四、深度分析(触发/补充)五、逐条优化建议汇总六、数据来源与生成时间

MySQL 慢查询日报 2026-10-22(staging)

统计口径:2026-10-22 00:00:00 ~ 23:59:59(Asia/Shanghai),ES @timestamp UTC 换算区间 [2026-10-22T00:00:00+08:00, 2026-10-23T00:00:00+08:00),env=staging。
数据来源:MCP es_slow_logs(Top10)+ es_search(高频模式,mysql_slow-*);MySQL 全程只读(connect / describe_schema / explain)。
生成时间:2026-10-23 10:00 +08:00。

一、统计概览

二、Top10 明细

#耗时(s)用户实例(server)SQL 摘要rows_sent / examined慢因判定
11572.7backupstaging/8891(LAN_addcn_84)SELECT * FROM t8891.t_item_modi_histories(mysqldump)5,693,964 / 5,693,964(EXPLAIN:ALL 全扫,~14G)大结果集传输(备份)
21156.5backupstaging/8891SELECT * FROM t8891.t_sele_item_infos3,290,762 / 3,290,762(ALL,~20G)大结果集传输(备份)
3489.0backupstaging/8891SELECT * FROM t8891.yahoo_car_details16,681 / 16,681(ALL,~18M,宽行大字段)大结果集传输(备份)
4350.5backupstaging/8891SELECT * FROM t8891.t_subscription_push39,105,741 / 39,105,741(ALL,~33G)大结果集传输(备份)
5328.1backupstaging/8891SELECT * FROM t8891.t_sele_item_photos22,929,970 / 22,929,970(ALL,~80G)大结果集传输(备份)
6309.5backupstaging/100-slave(LAN_addcn_46)SELECT * FROM t591.t1_daily_report30,309,750 / 30,309,750(ALL,~7G)大结果集传输(备份)
7290.6sonicstaging/8891commit;(rows_sent=0)0 / 0大事务提交(redo flush/IO 争用)
8287.5backupstaging/TD-slave(LAN_addcn_51)SELECT * FROM anylink.access_audit61,890,895 / 61,890,895(ALL,~72G)大结果集传输(备份)
9249.3backupstaging/tw8591(LAN_addcn_27_3307 → hk8591:3307)SELECT * FROM hk8591.h8_finance_account_logs13,603,238 / 13,603,238大结果集传输(备份)
10243.8backupstaging/TD-slaveSELECT * FROM anylink_corp.access_audit56,850,468 / 56,850,468(ALL,~65G)大结果集传输(备份)

Top10 判定说明:

三、高频慢查询模式(SQL 指纹聚合)

按条数 Top5

#条数平均(s)最大(s)累计用户serverSQL 骨架备注
11714.60290.613.1m8591/addcn8891_test/bee/chenruijia/jumper_dev/sonic27/37/84commit;大事务提交,深度分析✔
21131.452.992.7mjmysql27_3307/37/40_3308/46SHOW ENGINE INNODB STATUS;监控采集,非业务 SQL
31091.051.211.9ma859127SELECT a.id,... FROM gameList a LEFT JOIN hitCount_month b ...深度分析✔
4911.704.812.6m8591/jmysql27/46# administrator command: Ping;连接池 Ping,非 SQL
5721.624.531.9m859127rollback;回滚,反映事务冲突/超时

按累计耗时 Top5

#条数平均(s)最大(s)累计用户serverSQL 骨架备注
111572.71572.726.2mbackup84SELECT * FROM t8891.t_item_modi_histories【备份模式】
211156.51156.519.3mbackup84SELECT * FROM t8891.t_sele_item_infos【备份模式】
31714.60290.613.1m多用户27/37/84commit;大事务提交
4791.9196.610.7mt889184/*memberPoint*/SELECT COUNT(DISTINCT a.order_no) FROM t_sale_order_item a,t_sale_order b WHERE ...补充深挖✔
51533.1108.48.3m859127_3307SELECT sum(after_amount-before_amount) FROM h8_finance_account_logs WHERE user_id=? AND sub_account=?补充深挖✔

backup 模式说明:昨日各备份指纹均为单条出现,条数与历史常规持平,未触发深度分析。

四、深度分析(触发/补充)

4.1 commit;(171 条,累计 13.1m)— 触发:条数>100

4.2 SHOW ENGINE INNODB STATUS;(113 条)— 触发:条数>100

4.3 gameList 联查(109 条,avg 1.05s)— 触发:条数>100

4.4(补充)h8_finance_account_logs 余额求和(15 条,avg 33.1s,累计 8.3m)

4.5(补充)t_sale_order_item × t_sale_order COUNT(7 条,avg 91.9s,累计 10.7m)

4.6(补充)h8_orders buyer IN 批量查询(29 条,avg 2.35s)

五、逐条优化建议汇总

  1. 备份错峰与限流(全局最高优先):昨日 staging/8891 慢日志绝大多数耗时来自 backup 顺序导出大表(合计 >1.5h、~150G),并放大了 commit/监控语句延迟。建议 mysqldump 限流、错峰、大表(如 t_sele_item_photos 80G、access_audit 72G/65G、t_subscription_push 33G)改从 slave 备份或用物理备份。
  2. anylink / anylink_corp.access_audit 归档:两张审计表各 5~6 千万行且每天全量导出,建议按 created_at 分区/定期归档,备份只取增量。
  3. a8591.gameList:加 (type,parent_id) 索引;find_in_set('denyShow',setInfo) 改独立标志列。
  4. hk8591.h8_finance_account_logs:确保 (user_id,sub_account) 复合索引生效并覆盖金额列;余额查询改快照/缓存。
  5. t8891.t_sale_order:加 (m_id,status[,order_no]) 组合索引;memberPoint 统计改增量。
  6. 大事务治理(8891):对 sonic/bee 等账号的批量写入分批提交,降低 commit 延迟与 undo 压力。

六、数据来源与生成时间