MySQL排序引發(fā)的思考

問題一:同一個sql執(zhí)行倒序和正序性能差別很大茸习,sql明細(xì)如下:
-- 表結(jié)構(gòu):
CREATE TABLE `tb_project_white_list` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT COMMENT '主鍵',
  `project_id` varchar(32) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL COMMENT '活動id',
  `partner_user_id` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL COMMENT '開發(fā)者用戶id',
  `gmt_create` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '創(chuàng)建時間',
  `gmt_modified` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT '更新時間',
  `group_id` varchar(64) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL DEFAULT '0' COMMENT '分組id',
  `partner_extra` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT '擴展字段',
  PRIMARY KEY (`id`),
  UNIQUE KEY `idx_project_group` (`project_id`,`group_id`,`partner_user_id`),
  KEY `idx_gmt` (`gmt_create`),
  KEY `idx_prj_uid` (`project_id`(20),`partner_user_id`(100)),
  KEY `idx_oo` (`gmt_modified`)
) ENGINE=InnoDB AUTO_INCREMENT=31853378 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci STATS_SAMPLE_PAGES=40;
 
-- 性能對比有l(wèi)imit限制廷支,差異很大:
MySQL [projectx]> SELECT id, project_id, partner_user_id, partner_extra, group_id   , gmt_create, gmt_modified FROM tb_project_white_list WHERE project_id = 'p13651f79'   AND group_id = '0' ORDER BY id  desc limit 10;   
10 rows in set (0.00 sec)  -- 倒序很快
 
MySQL [projectx]> SELECT id, project_id, partner_user_id, partner_extra, group_id   , gmt_create, gmt_modified FROM tb_project_white_list WHERE project_id = 'p13651f79'   AND group_id = '0' ORDER BY id  asc limit 10;     
10 rows in set (5.03 sec) -- 正序異常慢
 
-- 性能對比沒有l(wèi)imit限制瓦呼,兩者幾乎一樣:
 
MySQL [projectx]> SELECT id, project_id, partner_user_id, partner_extra, group_id   , gmt_create, gmt_modified FROM tb_project_white_list WHERE project_id = 'p13651f79'   AND group_id = '0' ORDER BY id  desc;   
168023 rows in set (0.33 sec)  -- 倒序
 
MySQL [projectx]> SELECT id, project_id, partner_user_id, partner_extra, group_id   , gmt_create, gmt_modified FROM tb_project_white_list WHERE project_id = 'p13651f79'   AND group_id = '0' ORDER BY id  asc;     
168023 rows in set (0.36 sec) -- 正序
 
-- 不同sql形式 執(zhí)行計劃區(qū)別:
-- 1划咐、沒有l(wèi)imit:
 
MySQL [projectx]> desc SELECT id, project_id, partner_user_id, partner_extra, group_id   , gmt_create, gmt_modified FROM tb_project_white_list WHERE project_id = 'p13651f79'   AND group_id = '0' ORDER BY id desc;
+----+-------------+-----------------------+------------+------+-------------------------------+-------------+---------+-------+--------+----------+-----------------------------+
| id | select_type | table                 | partitions | type | possible_keys                 | key         | key_len | ref   | rows   | filtered | Extra                       |
+----+-------------+-----------------------+------------+------+-------------------------------+-------------+---------+-------+--------+----------+-----------------------------+
|  1 | SIMPLE      | tb_project_white_list | NULL       | ref  | idx_project_group,idx_prj_uid | idx_prj_uid | 62      | const | 337324 |    10.00 | Using where; Using filesort |
+----+-------------+-----------------------+------------+------+-------------------------------+-------------+---------+-------+--------+----------+-----------------------------+
1 row in set, 1 warning (0.00 sec)
 
MySQL [projectx]> desc  SELECT id, project_id, partner_user_id, partner_extra, group_id   , gmt_create, gmt_modified FROM tb_project_white_list WHERE project_id = 'p13651f79'   AND group_id = '0' ORDER BY id  asc;
+----+-------------+-----------------------+------------+------+-------------------------------+-------------+---------+-------+--------+----------+-----------------------------+
| id | select_type | table                 | partitions | type | possible_keys                 | key         | key_len | ref   | rows   | filtered | Extra                       |
+----+-------------+-----------------------+------------+------+-------------------------------+-------------+---------+-------+--------+----------+-----------------------------+
|  1 | SIMPLE      | tb_project_white_list | NULL       | ref  | idx_project_group,idx_prj_uid | idx_prj_uid | 62      | const | 337324 |    10.00 | Using where; Using filesort |
+----+-------------+-----------------------+------------+------+-------------------------------+-------------+---------+-------+--------+----------+-----------------------------+
1 row in set, 1 warning (0.00 sec)
 
-- 2熟史、有l(wèi)imit限制:
 
MySQL [projectx]> desc SELECT id, project_id, partner_user_id, partner_extra, group_id   , gmt_create, gmt_modified FROM tb_project_white_list WHERE project_id = 'p13651f79'   AND group_id = '0' ORDER BY id   desc limit 10;
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+----------------------------------+
| id | select_type | table                 | partitions | type  | possible_keys                 | key     | key_len | ref  | rows | filtered | Extra                            |
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+----------------------------------+
|  1 | SIMPLE      | tb_project_white_list | NULL       | index | idx_project_group,idx_prj_uid | PRIMARY | 8       | NULL |  392 |     2.65 | Using where; Backward index scan |
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+----------------------------------+
1 row in set, 1 warning (0.01 sec)
 
MySQL [projectx]> desc SELECT id, project_id, partner_user_id, partner_extra, group_id   , gmt_create, gmt_modified FROM tb_project_white_list WHERE project_id = 'p13651f79'   AND group_id = '0' ORDER BY id asc limit 10; 
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+-------------+
| id | select_type | table                 | partitions | type  | possible_keys                 | key     | key_len | ref  | rows | filtered | Extra       |
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+-------------+
|  1 | SIMPLE      | tb_project_white_list | NULL       | index | idx_project_group,idx_prj_uid | PRIMARY | 8       | NULL |  392 |     2.65 | Using where |
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+-------------+
 
-- 從執(zhí)行計劃可以看出有l(wèi)imit限制的sql選擇了主鍵掃描箱熬,基于不同排序規(guī)則差別在于:
這個表的單行數(shù)據(jù)大小約100B类垦,總1000W數(shù)據(jù)兩層索引樹就能存下,而select字句的查詢列超過了max_length_for_sort_data的長度城须,所以mysql選擇了代價較小的掃主鍵的方式避免filesort蚤认,
而project_id = 'p13651f79'的數(shù)據(jù)group_id全部為0并且id集中分布在索引樹右側(cè),desc下從右開始掃描糕伐,根節(jié)點和葉節(jié)點掃面的數(shù)據(jù)頁相對較少砰琢,并且8.0還使用了Backward index scan(索引倒序)做了進一步優(yōu)化。
問題二:為何在DMS上根據(jù)主鍵回表查詢正序和倒序也很慢?

原因:DMS在執(zhí)行sql時默認(rèn)會控制返回行數(shù)100條陪汽,實際在mysql-server中執(zhí)行會 SET SQL_SELECT_LIMIT=200训唱,所以看執(zhí)行計劃使用了idx_prj_uid,但實際執(zhí)行卻是掃描了主鍵挚冤,就會出現(xiàn)問題一中的現(xiàn)象况增。

DMS執(zhí)行流程:
-- 實際測試sql:
SELECT * FROM `rds_db_info`
 
-- DMS執(zhí)行邏輯:
220302 12:25:59    40 Query     show variables like '%character_set_results%'
                   40 Query     /* Query from DMS-WEBSQL-0-Qid_1646195158245 by user 262459518802646572 */ explain SELECT * FROM `rds_db_info`
                   40 Query     SET autocommit=1
                   40 Query     SET SQL_SELECT_LIMIT=200 --這里會做變量重置
                   40 Query     show variables like '%character_set_results%'
                   40 Query     SET SQL_SELECT_LIMIT=10
                   40 Query     /* Query from DMS-WEBSQL-0-Qid_1646195158245 by user 262459518802646572 */ SELECT * FROM `rds_db_info`

測試詳情如下:

-- 控制變量:
MySQL [projectx]> SET SQL_SELECT_LIMIT=200;
Query OK, 0 rows affected (0.00 sec)
 
MySQL [projectx]> desc  SELECT id, project_id, partner_user_id, partner_extra, group_id   , gmt_create, gmt_modified FROM tb_project_white_list WHERE project_id = 'p13651f79'   AND group_id = '0' ORDER BY id  asc;
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+-------------+
| id | select_type | table                 | partitions | type  | possible_keys                 | key     | key_len | ref  | rows | filtered | Extra       |
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+-------------+
|  1 | SIMPLE      | tb_project_white_list | NULL       | index | idx_project_group,idx_prj_uid | PRIMARY | 8       | NULL | 7842 |     2.65 | Using where |
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+-------------+
1 row in set, 1 warning (0.01 sec)
 
 
MySQL [projectx]> desc  SELECT id, project_id, partner_user_id, partner_extra, group_id   , gmt_create, gmt_modified FROM tb_project_white_list WHERE project_id = 'p13651f79'   AND group_id = '0' ORDER BY id  asc limit 100; 
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+-------------+
| id | select_type | table                 | partitions | type  | possible_keys                 | key     | key_len | ref  | rows | filtered | Extra       |
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+-------------+
|  1 | SIMPLE      | tb_project_white_list | NULL       | index | idx_project_group,idx_prj_uid | PRIMARY | 8       | NULL | 4105 |     2.55 | Using where |
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+-------------+
1 row in set, 1 warning (0.00 sec)
 
 
MySQL [projectx]> desc  SELECT id, project_id, partner_user_id, partner_extra, group_id   , gmt_create, gmt_modified FROM tb_project_white_list WHERE project_id = 'p13651f79'   AND group_id = '0' ORDER BY id  desc  limit 100;
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+-------------+
| id | select_type | table                 | partitions | type  | possible_keys                 | key     | key_len | ref  | rows | filtered | Extra       |
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+-------------+
|  1 | SIMPLE      | tb_project_white_list | NULL       | index | idx_project_group,idx_prj_uid | PRIMARY | 8       | NULL | 4105 |     2.55 | Using where |
+----+-------------+-----------------------+------------+-------+-------------------------------+---------+---------+------+------+----------+-------------+
主鍵掃描 不同排序方式性能差別:
不同排序方式性能差別
如何消除filesort:
-- 增加project_id單列索引,這時where條件檢索project_id時本身主鍵id就是asc有序的训挡,所以不需要再內(nèi)存排序
 
MySQL [projectx]> explain  SELECT id, project_id, partner_user_id, partner_extra, group_id   , gmt_create, gmt_modified FROM tb_project_white_list WHERE project_id = 'p13651f79'   AND group_id = '0' ORDER BY id  asc;
+----+-------------+-----------------------+------------+------+----------------------------------------------+----------------+---------+-------+--------+----------+------------------------------------+
| id | select_type | table                 | partitions | type | possible_keys                                | key            | key_len | ref   | rows   | filtered | Extra                              |
+----+-------------+-----------------------+------------+------+----------------------------------------------+----------------+---------+-------+--------+----------+------------------------------------+
|  1 | SIMPLE      | tb_project_white_list | NULL       | ref  | idx_project_group,idx_prj_uid,idx_project_id | idx_project_id | 98      | const | 320814 |    10.00 | Using index condition; Using where |
+----+-------------+-----------------------+------------+------+----------------------------------------------+----------------+---------+-------+--------+----------+------------------------------------+
?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
  • 序言:七十年代末澳骤,一起剝皮案震驚了整個濱河市,隨后出現(xiàn)的幾起案子舍哄,更是在濱河造成了極大的恐慌宴凉,老刑警劉巖,帶你破解...
    沈念sama閱讀 217,907評論 6 506
  • 序言:濱河連續(xù)發(fā)生了三起死亡事件表悬,死亡現(xiàn)場離奇詭異,居然都是意外死亡丧靡,警方通過查閱死者的電腦和手機蟆沫,發(fā)現(xiàn)死者居然都...
    沈念sama閱讀 92,987評論 3 395
  • 文/潘曉璐 我一進店門,熙熙樓的掌柜王于貴愁眉苦臉地迎上來温治,“玉大人饭庞,你說我怎么就攤上這事“揪#” “怎么了舟山?”我有些...
    開封第一講書人閱讀 164,298評論 0 354
  • 文/不壞的土叔 我叫張陵,是天一觀的道長卤恳。 經(jīng)常有香客問我累盗,道長,這世上最難降的妖魔是什么突琳? 我笑而不...
    開封第一講書人閱讀 58,586評論 1 293
  • 正文 為了忘掉前任若债,我火速辦了婚禮,結(jié)果婚禮上拆融,老公的妹妹穿的比我還像新娘蠢琳。我一直安慰自己,他們只是感情好镜豹,可當(dāng)我...
    茶點故事閱讀 67,633評論 6 392
  • 文/花漫 我一把揭開白布傲须。 她就那樣靜靜地躺著,像睡著了一般趟脂。 火紅的嫁衣襯著肌膚如雪泰讽。 梳的紋絲不亂的頭發(fā)上,一...
    開封第一講書人閱讀 51,488評論 1 302
  • 那天,我揣著相機與錄音菇绵,去河邊找鬼肄渗。 笑死,一個胖子當(dāng)著我的面吹牛咬最,可吹牛的內(nèi)容都是我干的翎嫡。 我是一名探鬼主播,決...
    沈念sama閱讀 40,275評論 3 418
  • 文/蒼蘭香墨 我猛地睜開眼永乌,長吁一口氣:“原來是場噩夢啊……” “哼惑申!你這毒婦竟也來了?” 一聲冷哼從身側(cè)響起翅雏,我...
    開封第一講書人閱讀 39,176評論 0 276
  • 序言:老撾萬榮一對情侶失蹤圈驼,失蹤者是張志新(化名)和其女友劉穎,沒想到半個月后望几,有當(dāng)?shù)厝嗽跇淞掷锇l(fā)現(xiàn)了一具尸體绩脆,經(jīng)...
    沈念sama閱讀 45,619評論 1 314
  • 正文 獨居荒郊野嶺守林人離奇死亡,尸身上長有42處帶血的膿包…… 初始之章·張勛 以下內(nèi)容為張勛視角 年9月15日...
    茶點故事閱讀 37,819評論 3 336
  • 正文 我和宋清朗相戀三年橄抹,在試婚紗的時候發(fā)現(xiàn)自己被綠了靴迫。 大學(xué)時的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片。...
    茶點故事閱讀 39,932評論 1 348
  • 序言:一個原本活蹦亂跳的男人離奇死亡楼誓,死狀恐怖玉锌,靈堂內(nèi)的尸體忽然破棺而出,到底是詐尸還是另有隱情疟羹,我是刑警寧澤主守,帶...
    沈念sama閱讀 35,655評論 5 346
  • 正文 年R本政府宣布,位于F島的核電站榄融,受9級特大地震影響参淫,放射性物質(zhì)發(fā)生泄漏。R本人自食惡果不足惜剃袍,卻給世界環(huán)境...
    茶點故事閱讀 41,265評論 3 329
  • 文/蒙蒙 一黄刚、第九天 我趴在偏房一處隱蔽的房頂上張望。 院中可真熱鬧民效,春花似錦憔维、人聲如沸。這莊子的主人今日做“春日...
    開封第一講書人閱讀 31,871評論 0 22
  • 文/蒼蘭香墨 我抬頭看了看天上的太陽。三九已至舒萎,卻和暖如春程储,著一層夾襖步出監(jiān)牢的瞬間,已是汗流浹背。 一陣腳步聲響...
    開封第一講書人閱讀 32,994評論 1 269
  • 我被黑心中介騙來泰國打工章鲤, 沒想到剛下飛機就差點兒被人妖公主榨干…… 1. 我叫王不留摊灭,地道東北人。 一個月前我還...
    沈念sama閱讀 48,095評論 3 370
  • 正文 我出身青樓败徊,卻偏偏與公主長得像帚呼,于是被迫代替她去往敵國和親。 傳聞我的和親對象是個殘疾皇子皱蹦,可洞房花燭夜當(dāng)晚...
    茶點故事閱讀 44,884評論 2 354

推薦閱讀更多精彩內(nèi)容