MYSQL 阿里的一个sql优化问题

千家信息网最后更新 2025年02月23日MYSQL 阿里的一个sql优化问题原创水平有限，如果有误请指出

今天研究了一天innodb事物，临近下班了同事田兴春告诉我有个阿里发出来的优化题，并且把建表和语句给我了，并且告诉我语句里面有隐式转换
昨天群里也有人说这道题但是一直没空看，刚好这会没事就看了一下，整个脚本如下：

点击(此处)折叠或打开

1. 数据准备：
   
2. 
   
3. create table a (id int auto_increment,seller_id bigint,seller_name varchar(100) collate utf8_bin ,gmt_create varchar(30),primary key(id));
   
4. 
   
5. insert into a (seller_id,seller_name,gmt_create) values (100000,'uniqla','2017-01-01');
   
6. insert into a (seller_id,seller_name,gmt_create) values (100001,'uniqlb','2017-02-01');
   
7. insert into a (seller_id,seller_name,gmt_create) values (100002,'uniqlc','2017-03-01');
   
8. insert into a (seller_id,seller_name,gmt_create) values (100003,'uniqld','2017-04-01');
   
9. insert into a (seller_id,seller_name,gmt_create) values (100004,'uniqle','2017-05-01');
   
10. insert into a (seller_id,seller_name,gmt_create) values (100005,'uniqlf','2017-06-01');
    
11. insert into a (seller_id,seller_name,gmt_create) values (100006,'uniqlg','2017-07-01');
    
12. insert into a (seller_id,seller_name,gmt_create) values (100007,'uniqlh','2017-08-01');
    
13. insert into a (seller_id,seller_name,gmt_create) values (100008,'uniqli','2017-09-01');
    
14. insert into a (seller_id,seller_name,gmt_create) values (100009,'uniqlj','2017-10-01');
    
15. insert into a (seller_id,seller_name,gmt_create) values (100010,'uniqlk','2017-11-01');
    
16. insert into a (seller_id,seller_name,gmt_create) values (100011,'uniqll','2017-12-01');
    
17. insert into a (seller_id,seller_name,gmt_create) values (100012,'uniqlm','2018-01-01');
    
18. insert into a (seller_id,seller_name,gmt_create) values (100013,'uniqln','2018-02-01');
    
19. insert into a (seller_id,seller_name,gmt_create) values (100014,'uniqlo','2018-03-01');
    
20. insert into a (seller_id,seller_name,gmt_create) values (100015,'uniqlp','2018-04-01');
    
21. 
    
22. insert into a (seller_id,seller_name,gmt_create) select seller_id,seller_name,gmt_create from a;
    
23. insert into a (seller_id,seller_name,gmt_create) select seller_id,seller_name,gmt_create from a;
    
24. insert into a (seller_id,seller_name,gmt_create) select seller_id,seller_name,gmt_create from a;
    
25. insert into a (seller_id,seller_name,gmt_create) select seller_id,seller_name,gmt_create from a;
    
26. insert into a (seller_id,seller_name,gmt_create) select seller_id,seller_name,gmt_create from a;
    
27. insert into a (seller_id,seller_name,gmt_create) select seller_id,seller_name,gmt_create from a;
    
28. insert into a (seller_id,seller_name,gmt_create) select seller_id,seller_name,gmt_create from a;
    
29. insert into a (seller_id,seller_name,gmt_create) select seller_id,seller_name,gmt_create from a;
    
30. insert into a (seller_id,seller_name,gmt_create) select seller_id,seller_name,gmt_create from a;
    
31. insert into a (seller_id,seller_name,gmt_create) select seller_id,seller_name,gmt_create from a;
    
32. 
    
33. insert into a (seller_id,seller_name,gmt_create) values (100016,'uniqlq',now());
    
34. 
    
35. create table b (id int auto_increment,seller_name varchar(100),user_id varchar(50),user_name varchar(100),sales bigint,gmt_create varchar(30),primary key(id));
    
36. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqla','1','a',1,now());
    
37. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqlb','2','b',3,now());
    
38. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqlc','3','c',1,now());
    
39. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqld','4','d',4,now());
    
40. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqle','5','e',5,now());
    
41. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqlf','6','f',1,now());
    
42. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqlg','7','g',7,now());
    
43. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqlh','8','h',1,now());
    
44. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqli','9','i',1,now());
    
45. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqlj','10','j',15,now());
    
46. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqlk','11','k',61,now());
    
47. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqll','12','l',31,now());
    
48. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqlm','13','m',134,now());
    
49. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqln','14','n',1455,now());
    
50. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqlo','15','o',166,now());
    
51. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('niqlp','16','p',15,now());
    
52. 
    
53. 
    
54. insert into b (seller_name,user_id,user_name,sales,gmt_create) select seller_name,user_id,user_name,sales,gmt_create from b;
    
55. insert into b (seller_name,user_id,user_name,sales,gmt_create) select seller_name,user_id,user_name,sales,gmt_create from b;
    
56. insert into b (seller_name,user_id,user_name,sales,gmt_create) select seller_name,user_id,user_name,sales,gmt_create from b;
    
57. insert into b (seller_name,user_id,user_name,sales,gmt_create) select seller_name,user_id,user_name,sales,gmt_create from b;
    
58. insert into b (seller_name,user_id,user_name,sales,gmt_create) select seller_name,user_id,user_name,sales,gmt_create from b;
    
59. insert into b (seller_name,user_id,user_name,sales,gmt_create) select seller_name,user_id,user_name,sales,gmt_create from b;
    
60. insert into b (seller_name,user_id,user_name,sales,gmt_create) select seller_name,user_id,user_name,sales,gmt_create from b;
    
61. insert into b (seller_name,user_id,user_name,sales,gmt_create) select seller_name,user_id,user_name,sales,gmt_create from b;
    
62. insert into b (seller_name,user_id,user_name,sales,gmt_create) select seller_name,user_id,user_name,sales,gmt_create from b;
    
63. insert into b (seller_name,user_id,user_name,sales,gmt_create) select seller_name,user_id,user_name,sales,gmt_create from b;
    
64. 
    
65. 
    
66. 
    
67. 
    
68. insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('uniqlq','17','s',109,now());
    
69. 
    
70. 
    
71. 
    
72. 
    
73. 
    
74. create table c (id int auto_increment,user_id varchar(50),order_id varchar(100),state bigint,gmt_create varchar(30),primary key(id));
    
75. insert into c (user_id,order_id,state,gmt_create) values( 21,1,0 ,now() );
    
76. insert into c (user_id,order_id,state,gmt_create) values( 22,2,0 ,now() );
    
77. insert into c (user_id,order_id,state,gmt_create) values( 33,3,0 ,now() );
    
78. insert into c (user_id,order_id,state,gmt_create) values( 43,4,0 ,now() );
    
79. insert into c (user_id,order_id,state,gmt_create) values( 54,5,0 ,now() );
    
80. insert into c (user_id,order_id,state,gmt_create) values( 65,6,0 ,now() );
    
81. insert into c (user_id,order_id,state,gmt_create) values( 75,7,0 ,now() );
    
82. insert into c (user_id,order_id,state,gmt_create) values( 85,8,0 ,now() );
    
83. insert into c (user_id,order_id,state,gmt_create) values( 95,8,0 ,now() );
    
84. insert into c (user_id,order_id,state,gmt_create) values( 100,8,0 ,now() );
    
85. insert into c (user_id,order_id,state,gmt_create) values( 150,8,0 ,now() );
    
86. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
    
87. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
    
88. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
    
89. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
    
90. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
    
91. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
    
92. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
    
93. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
    
94. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
    
95. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
    
96. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
    
97. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
    
98. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
    
99. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
    
100. insert into c (user_id,order_id,state,gmt_create) select user_id,order_id,state,gmt_create from c;
     
101. 
     
102. 
     
103. 
     
104. insert into c (user_id,order_id,state,gmt_create) values( 17,8,0 ,now() );
     
105. 
     
106. 
     
107. 
     
108. 待优化SQL：
     
109. select a.seller_id,a.seller_name,b.user_name,c.state
     
110. from a,b,c
     
111. where a.seller_name=b.seller_name
     
112. and b.user_id=c.user_id
     
113. and c.user_id=17
     
114. and a.gmt_create BETWEEN DATE_ADD(NOW(), INTERVAL - 600 MINUTE)
     
115. AND DATE_ADD(NOW(), INTERVAL 600 MINUTE)
     
116. order by a.gmt_create

先说明这个优化题目主要考察下面5点：
1、BNL和NJL的区别
2、NJL的实现
3、DBA对于数据分布的观察
4、隐式转换索引不能使用
5、比较字符集不同索引不能使用

一、我们先来分别描述
1、BNL和NJL的区别
这个区别参考我的文章
http://blog.itpub.net/7728585/viewspace-2129502/
(从顺序随机I/O原理来讨论MYSQL MRR NLJ BNL BKA )
简单的说BNL一般用于TYPE=INDEX以及TYPE=ALL的情况，因为被驱动表连接条件没有索引，而需要join buffer 将驱动表中待连接的
数据取出来(物理/逻辑 读取)，放到join buffer，主要目的在于减少被驱动表的驱动次数，从而提高效率，因为没有索引的情况
被驱动表扫描一次实在太慢了，这里的B就是BLOCK的意思.
而NJL一般用于被驱动表连接条件有索引的情况，通过索引上的ref或者eq_ref(取决于索引是否唯一)就理所当然的快很多很多，这个时候join buffer是不会
使用的，它只需要读取一条数据(物理/逻辑 读取)来驱动一次驱动表，因为驱动表连接条件有索引，自然就快了(索引定位回表)
2、NJL的实现
同样可以参考上面的文章，上面也大概说了一下，就不在废话了
3、DBA对于数据分布的观察
这一点是人为可以达到的，简单的说比如一个表有100条数据 99条为no=1 1条为no=2，那么我们
需要对这个有所警觉，如果这个表示用作驱动表那么no=2的时候效果要远远好于no=1。这道题也有
这个因素
明显and c.user_id='17' 只有一条数据
4、隐式转换索引不能使用
这个不管是MYSQL还是ORACLE都有的问题，
ORACLE会显示给出来to_char(id)='1'之类的
MYSQL中会有如下类似的警告
| Warning | 1739 | Cannot use ref access on index 'user_id' due to type or collation conversion on field 'user_id' |
| Warning | 1739 | Cannot use range access on index 'user_id' due to type or collation conversion on field 'user_id'

比如这里的
c.user_id=17
而
user_id 是varchar类型不是int类型
又比如这里的
a.gmt_create BETWEEN DATE_ADD(NOW(), INTERVAL - 600 MINUTE)
AND DATE_ADD(NOW(), INTERVAL 600 MINUTE)
这里
gmt_create varchar(30) 居然也是varchar 擦！！
5、比较字符集不同索引使用异常
这个关于字符串的比较问题我已经在文章里面有所描述
http://blog.itpub.net/7728585/viewspace-2141914/
简单的说这里
a.seller_name=b.seller_name
a.seller_name 比较字符集是utf8_bin 区分大小写
而
b.seller_name 是不区分大小写的这是默认的。
他们之间做join必然被驱动表用不到索引使用异常。(innodb 可以icp)
也会有类似如下的警告：
Cannot use ref access on index 'seller_name' due to type or collation conversion on field 'seller_name'

二、优化原则问题
我们知道基本所有的语句执行算法逻辑都在MYSQL层次，INNODB只是负责将数据通过几种方式
(PAGE_CUR_G，PAGE_CUR_GE，PAGE_CUR_L，PAGE_CUR_LE)扫描出来，递送给MYSQL层次进行处理，这之间存在扫描拿到
innodb record-->innodb tuple-->mysql record的一个转换的过程，这个步骤大部分被标记为sending data过程
(update/delete为updating)，那么我们就有必要减少中间结果集的产生，来减少整个从innodb拿数据到MYSQL层的
整个数据量。这里以NJL的优化原则为列解释，因为这道题就是这个目的

1、减少NJL驱动结果集的数据
这事显而易见的，减少驱动次数自然就减少了数据在innodb和mysql之间的传递
2、被驱动表的索引唯一性要尽量好
这个问题稍微难理解一点，但是仔细想一下也没什么，如果被驱动表索引唯一性更好，那么通过索引回表的次数就少了，
这里可以通过rows和filter进行大概判断，大概是因为他们本来就不准。
曾经我们就有一个列子也是同事田兴春和我一起看的。一个被驱动表有两个链接条件，一个索引唯一性很差，而唯一性好的连接
列上没有索引，我们在唯一性好的列上建立了索引性能马上提升了。

三、关于本题

我们还是先避免c.user_id=17 隐试转换将17改为'17',a.gmt_create没有必要改他，原因后面会说
select a.seller_id,a.seller_name,b.user_name,c.state
from a,b,c
where a.seller_name=b.seller_name
and b.user_id=c.user_id
and c.user_id='17'
and a.gmt_create BETWEEN DATE_ADD(NOW(), INTERVAL - 600 MINUTE)
AND DATE_ADD(NOW(), INTERVAL 600 MINUTE)
order by a.gmt_create

然后我们看一下执行计划
+----+-------------+-------+------------+------+---------------+------+---------+------+--------+----------+----------------------------------------------------+
| id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+----+-------------+-------+------------+------+---------------+------+---------+------+--------+----------+----------------------------------------------------+
| 1 | SIMPLE | a | NULL | ALL | NULL | NULL | NULL | NULL | 16108 | 11.11 | Using where; Using temporary; Using filesort |
| 1 | SIMPLE | b | NULL | ALL | NULL | NULL | NULL | NULL | 16173 | 10.00 | Using where; Using join buffer (Block Nested Loop) |
| 1 | SIMPLE | c | NULL | ALL | NULL | NULL | NULL | NULL | 359382 | 1.00 | Using where; Using join buffer (Block Nested Loop) |
+----+-------------+-------+------------+------+---------------+------+---------+------+--------+----------+----------------------------------------------------+
3 rows in set, 1 warning (0.02 sec)

这里使用BNL，这事正常的连接条件没有任何索引，同时我们开始观察数据发现这道题
c表最后插入了
insert into c (user_id,order_id,state,gmt_create) values( 17,8,0 ,now() );
b表最后插入了
insert into b (seller_name,user_id,user_name,sales,gmt_create) values ('uniqlq','17','s',109,now());
a表最后插入了
insert into a (seller_id,seller_name,gmt_create) values (100016,'uniqlq',now());
我们可以发现整个语句不管a,b,c表数据量有多大，整个连接下来只有一条数据，这也是我说的DBA对于数据分布观察的问题
，按照最优化的方法通过c表c.user_id='17'过滤后得到一个驱动结果集(实际上这里b表也可以MYSQL自动转换了)只有一条数据
然后连接b表（b.user_id=c.user_id）自然中间驱动结果集也只有一条数据，最后通过（a.seller_name=b.seller_name）连接
a表自然就只有一条数据了
and a.gmt_create BETWEEN DATE_ADD(NOW(), INTERVAL - 600 MINUTE)
AND DATE_ADD(NOW(), INTERVAL 600 MINUTE)
order by a.gmt_create
这两个都不用管它了。

按照这个思想。
我们可以先在c.user_id建立一个索引，意图在于通过索引过滤掉 c.user_id='17'， b.user_id建立索引意图在于NJL被驱动表使用索引而不是全表的BNL
执行计划变为:

点击(此处)折叠或打开

1. mysql> desc select a.seller_id,a.seller_name,b.user_name,c.state from a,b,c where a.seller_name=b.seller_name and b.user_id=c.user_id and c.user_id='17' and a.gmt_create BETWEEN DATE_ADD(NOW(), INTERVAL - 600 MINUTE) AND
   
2. 
   
3. DATE_ADD(NOW(), INTERVAL 600 MINUTE) order by a.gmt_create;
   
4. +----+-------------+-------+------------+------+---------------+---------+---------+-------+-------+----------+----------------------------------------------------+
   
5. | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
   
6. +----+-------------+-------+------------+------+---------------+---------+---------+-------+-------+----------+----------------------------------------------------+
   
7. | 1 | SIMPLE | b | NULL | ref | user_id | user_id | 153 | const | 1 | 100.00 | Using temporary; Using filesort |
   
8. | 1 | SIMPLE | c | NULL | ref | user_id | user_id | 153 | const | 1 | 100.00 | Using index condition |
   
9. | 1 | SIMPLE | a | NULL | ALL | NULL | NULL | NULL | NULL | 16108 | 1.11 | Using where; Using join buffer (Block Nested Loop) |
   
10. +----+-------------+-------+------------+------+---------------+---------+---------+-------+-------+----------+----------------------------------------------------+

显然这里b.user_id=c.user_id and c.user_id='17' 有一个转换如下我们通过sql trace可以看到

"resulting_condition": "((`a`.`seller_name` = `b`.`seller_name`) and (`c`.`user_id` = '17') and (`a`.`gmt_create` between (now() + interval -(600) minute) and (now() + interval 600 minute)) and multiple equal(`b`.`user_id`, `c`.`user_id`))"
我们可以注意这里的
multiple equal(`b`.`user_id`, `c`.`user_id`))"
这实际上进行了转换 因为显然的b.user_id='17'是成立的

剩下的就是解决a表的BNL问题。我们不能让a表进行type=ALL 全表扫描，从而加快速度
我们在a.seller_name和b.seller_name建立索引执行计划变成了

点击(此处)折叠或打开

1. mysql> desc select a.seller_id,a.seller_name,b.user_name,c.state from a,b,c where a.seller_name=b.seller_name and b.user_id=c.user_id and c.user_id='17' and a.gmt_create BETWEEN DATE_ADD(NOW(), INTERVAL - 600 MINUTE) AND
   
2. 
   
3. DATE_ADD(NOW(), INTERVAL 600 MINUTE) order by a.gmt_create;
   
4. +----+-------------+-------+------------+------+---------------------+-------------+---------+--------------------+------+----------+----------------------------------------------+
   
5. | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
   
6. +----+-------------+-------+------------+------+---------------------+-------------+---------+--------------------+------+----------+----------------------------------------------+
   
7. | 1 | SIMPLE | b | NULL | ref | user_id,seller_name | user_id | 153 | const | 1 | 100.00 | Using where; Using temporary; Using filesort |
   
8. | 1 | SIMPLE | c | NULL | ref | user_id | user_id | 153 | const | 1 | 100.00 | Using index condition |
   
9. | 1 | SIMPLE | a | NULL | ref | seller_name | seller_name | 303 | test.b.seller_name | 947 | 11.11 | Using index condition; Using where |
   
10. +----+-------------+-------+------------+------+---------------------+-------------+---------+--------------------+------+----------+----------------------------------------------+
11. 3 rows in set, 2 warnings (0.00 sec)
    

这个时候我们看起来使用到了索引，但是这是ICP的功劳，我们看警告
Cannot use ref access on index 'seller_name' due to type or collation conversion on field 'seller_name'
这也就是我说的比较字符集不同索引使用异常，为了消除这个问题我们不得不更改a表seller_name的比较字符集

最后我们得到执行计划

点击(此处)折叠或打开

1. +----+-------------+-------+------------+------+---------------------+-------------+---------+--------------------+------+----------+----------------------------------------------+
   
2. | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
   
3. +----+-------------+-------+------------+------+---------------------+-------------+---------+--------------------+------+----------+----------------------------------------------+
   
4. | 1 | SIMPLE | b | NULL | ref | user_id,seller_name | user_id | 153 | const | 1 | 100.00 | Using where; Using temporary; Using filesort |
   
5. | 1 | SIMPLE | c | NULL | ref | user_id | user_id | 153 | const | 1 | 100.00 | Using index condition |
   
6. | 1 | SIMPLE | a | NULL | ref | seller_name | seller_name | 303 | test.b.seller_name | 1 | 11.11 | Using where |
   
7. +----+-------------+-------+------------+------+---------------------+-------------+---------+--------------------+------+----------+----------------------------------------------+

这下一切都正常了，Using index condition ICP没有了，只有一个where了这个where显然是
a.gmt_create BETWEEN DATE_ADD(NOW(), INTERVAL - 600 MINUTE)
AND DATE_ADD(NOW(), INTERVAL 600 MINUTE)
至于
Using temporary; Using filesort
我们可以不理他了一条数据而已

至此优化结束。
优化后profile
+----------------------+----------+----------+------------+
| Status | Duration | CPU_user | CPU_system |
+----------------------+----------+----------+------------+
| starting | 0.000169 | 0.000000 | 0.000000 |
| checking permissions | 0.000005 | 0.000000 | 0.000000 |
| checking permissions | 0.000006 | 0.000000 | 0.000000 |
| checking permissions | 0.000005 | 0.000000 | 0.000000 |
| Opening tables | 0.000026 | 0.000000 | 0.000000 |
| init | 0.000055 | 0.000000 | 0.000000 |
| System lock | 0.000013 | 0.000000 | 0.000000 |
| optimizing | 0.000018 | 0.000000 | 0.000000 |
| statistics | 0.000118 | 0.000000 | 0.000000 |
| preparing | 0.000022 | 0.000000 | 0.000000 |
| Creating tmp table | 0.000030 | 0.000000 | 0.000000 |
| Sorting result | 0.000007 | 0.000000 | 0.000000 |
| executing | 0.000003 | 0.000000 | 0.000000 |
| Sending data | 0.000101 | 0.000000 | 0.000000 |
| Creating sort index | 0.000027 | 0.000000 | 0.000000 |
| end | 0.000004 | 0.000000 | 0.000000 |
| query end | 0.000059 | 0.001000 | 0.000000 |
| removing tmp table | 0.000096 | 0.000000 | 0.000000 |
| query end | 0.000004 | 0.000000 | 0.000000 |
| closing tables | 0.000008 | 0.000000 | 0.000000 |
| freeing items | 0.000018 | 0.000000 | 0.000000 |
| cleaning up | 0.000022 | 0.000000 | 0.000000 |
+----------------------+----------+----------+------------+


这是之前的profile


+----------------------+----------+----------+------------+
| Status | Duration | CPU_user | CPU_system |
+----------------------+----------+----------+------------+
| starting | 0.000226 | 0.000000 | 0.000000 |
| checking permissions | 0.000011 | 0.000000 | 0.000000 |
| checking permissions | 0.000006 | 0.000000 | 0.000000 |
| checking permissions | 0.000014 | 0.000000 | 0.000000 |
| checking permissions | 0.000006 | 0.000000 | 0.000000 |
| checking permissions | 0.000004 | 0.000000 | 0.000000 |
| checking permissions | 0.000007 | 0.000000 | 0.000000 |
| Opening tables | 0.000039 | 0.000000 | 0.000000 |
| init | 0.000238 | 0.001000 | 0.000000 |
| System lock | 0.000029 | 0.000000 | 0.000000 |
| optimizing | 0.000118 | 0.000000 | 0.000000 |
| statistics | 0.000176 | 0.000000 | 0.000000 |
| preparing | 0.000112 | 0.000000 | 0.000000 |
| Creating tmp table | 0.000052 | 0.000000 | 0.000000 |
| Sorting result | 0.000019 | 0.000000 | 0.000000 |
| executing | 0.000005 | 0.000000 | 0.000000 |
| Sending data | 0.231418 | 0.230965 | 0.000000 |
| Creating sort index | 0.000055 | 0.000000 | 0.000000 |
| end | 0.000006 | 0.000000 | 0.000000 |
| query end | 0.000012 | 0.000000 | 0.000000 |
| removing tmp table | 0.000005 | 0.000000 | 0.000000 |
| query end | 0.000004 | 0.000000 | 0.000000 |
| closing tables | 0.000011 | 0.000000 | 0.000000 |
| freeing items | 0.000347 | 0.000000 | 0.000000 |
| cleaning up | 0.000015 | 0.000000 | 0.000000 |
+----------------------+----------+----------+------------+
很显然这里Sending data太久，也就是我前面说的innodb和mysql之间数据交互的问题。

作者微信: