-
Sending data
The thread is processing rows for a statement and also is sending data to the client.
開始一直以爲是max_allow_packet的值太小,並且認爲程序有問題導致tomcat響應很慢。mysql 將查詢的結果發送給前端tomcat.而此時tomcat因程序問題響應很慢,所以mysql將查詢到的結果一直處理Sending data狀態。但是讓我不明白的是我前端有兩個同樣的tomcat,爲什麼同時都有問題。
後來仔細分析了兩次出現大量Sending data的sql語句。發現大部分都是針對一個表上的查詢。而且where 條件的那個字段值只有幾種,大部分都是相同的值。這樣在上面建索引根本沒有任何的效果。同時用profile驗證了這個sql查詢每個階段所需要的時間。發現在Sending data 上花費的時間最長。expalin 出來的結果顯示共掃描了161172行。
mysql> explain select P.ID_ FROM NEWSFEEDDIST P WHERE RELATIONSHIP_ = 1 and CREATED_ >= DATE_SUB(NOW(),INTERVAL 18 DAY) AND CREATED_ < DATE_SUB(NOW(),INTERVAL 17 DAY); +----+-------------+-------+------+-------------------------+-------------------------+---------+-------+--------+-------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+-------+------+-------------------------+-------------------------+---------+-------+--------+-------------+
| 1 | SIMPLE | P | ref | SNS_NEWSFEEDDIST_REL_IN | SNS_NEWSFEEDDIST_REL_IN | 3 | const | 161172 | Using where |
+----+-------------+-------+------+-------------------------+-------------------------+---------+-------+--------+-------------+
mysql> set profiling =1;
mysql> SELECT COUNT(1), MAX(P.CREATED_) FROM NEWSFEEDDIST P WHERE RELATIONSHIP_ = 1 AND CREATED_ >= DATE_SUB(NOW(),INTERVAL 19 DAY) AND CREATED_ < DATE_SUB(NOW(),INTERVAL 18 DAY);
mysql> show profile for query 1;
+--------------------------------+----------+
| Status | Duration |
+--------------------------------+----------+
| starting | 0.060039 |
| checking query cache for query | 0.000161 |
| Opening tables | 0.000034 |
| System lock | 0.000019 |
| Table lock | 0.000021 |
| init | 0.000095 |
| optimizing | 0.000035 |
| statistics | 0.000157 |
| preparing | 0.000040 |
| executing | 0.000010 |
| Sending data | 1.079902 |
| end | 0.000018 |
| query end | 0.000005 |
| freeing items | 0.000056 |
| logging slow query | 0.000004 |
| logging slow query | 0.000053 |
| cleaning up | 0.000007 |
+--------------------------------+----------+
17 rows in set (0.00 sec)
既然 RELATIONSHIP_ 字段上的索引無效,那麼針對這個sql我在CREATED_字段上創建了一個索引。再次運行
mysql>alter table NEWSFEEDDIST add index(CREATED_);
mysql>SELECT COUNT(1), MAX(P.CREATED_) FROM NEWSFEEDDIST P WHERE RELATIONSHIP_ = 1 AND CREATED_ >= DATE_SUB(NOW(),INTERVAL 19 DAY) AND CREATED_ < DATE_SUB(NOW(),INTERVAL 18 DAY);
mysql>show profile for query 3;
+--------------------------------+----------+
| Status | Duration |
+--------------------------------+----------+
| starting | 0.000048 |
| checking query cache for query | 0.000130 |
| Opening tables | 0.000028 |
| System lock | 0.000011 |
| Table lock | 0.000019 |
| init | 0.000076 |
| optimizing | 0.000031 |
| statistics | 0.000183 |
| preparing | 0.000034 |
| executing | 0.000011 |
| Sending data | 0.007954 |
| end | 0.000013 |
| query end | 0.000009 |
| freeing items | 0.000088 |
| logging slow query | 0.000009 |
| cleaning up | 0.000011 |
+--------------------------------+----------+
16 rows in set (0.00 sec)
此時在sending data上小了很多。而且用了CREATED_索引後掃描的行數變成了2888條
mysql>explain select P.ID_ FROM test_NEWSFEEDDIST P WHERE RELATIONSHIP_ = 1 and CREATED_ >= DATE_SUB(NOW(),INTERVAL 18 DAY) AND CREATED_ < DATE_SUB(NOW(),INTERVAL 17 DAY);
+----+-------------+-------+-------+----------------------------------+----------+---------+------+------+-------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+-------+-------+----------------------------------+----------+---------+------+------+-------------+
| 1 | SIMPLE | P | range | SNS_NEWSFEEDDIST_REL_IN,CREATED_ | CREATED_ | 9 | NULL | 2888 | Using where |
+----+-------------+-------+-------+----------------------------------+----------+---------+------+------+-------------+
這個效果還是不錯的。cool
這裏有個關於mysql sending data狀態的解釋
http://renxijun.blog.sohu.com/82906360.html