对Group By 语句的一次优化过程
对Group By 语句的一次优化过程
对Group By 语句的一次优化过程
作者: fuyuncat
来源: www.HelloDBA.com
生产环境中发现一条语句很慢,拿回来一看,其实是一个简单的Group By语句:
表CCMMT的数据量比较大,5M多条记录。
1、
SQL> select CDE, CID
2 from CCMMT
3 GROUP BY CDE, CID
4 having max(ADT) < sysdate - 180;
707924 rows selected.
Elapsed: 00:06:17.49
Execution Plan
----------------------------------------------------------
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=414 Card=238583 Bytes=4771660)
1 0 FILTER
2 1 SORT (GROUP BY NOSORT) (Cost=414 Card=238583 Bytes=4771660)
3 2 TABLE ACCESS (BY INDEX ROWID) OF 'CCMMT' (Cost=414 Card=57969096 Bytes=1159381920)
4 3 INDEX (FULL SCAN) OF 'CCMMT_TEMP_IDX' (NON-UNIQUE) (Cost=26 Card=57969096)
Statistics
----------------------------------------------------------
0 recursive calls
0 db block gets
2769177 consistent gets
1089991 physical reads
0 redo size
23926954 bytes sent via SQL*Net to client
519785 bytes received via SQL*Net from client
47196 SQL*Net roundtrips to/from client
0 sorts (memory)
0 sorts (disk)
707924 rows processed
要6min多返回。尝试调整语句写法,用minus代替Group By:
2、
SQL> select DISTINCT CDE, CID
2 from CCMMT
3 where ADT < sysdate - 180
4 minus
5 select DISTINCT CDE, CID
6 from CCMMT
7 where ADT >= sysdate - 180;
707924 rows selected.
Elapsed: 00:00:21.53
Execution Plan
----------------------------------------------------------
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=190624 Card=2794940
Bytes=111797600)
1 0 MINUS
2 1 SORT* (UNIQUE) (Cost=95312 Card=2794940 Bytes=55898800) :Q13049001
3 2 INDEX* (FAST FULL SCAN) OF 'CCMMT_UQ1' (UNIQUE) (Cost=77305 Card=2898455 Bytes=57969100) :Q13049000
4 1 SORT* (UNIQUE) (Cost=95312 Card=2794940 Bytes=55898800) :Q13050001
5 4 INDEX* (FAST FULL SCAN) OF 'CCMMT_UQ1' (UNIQUE) (Cost=77305 Card=2898455 Bytes=57969100) :Q13050000
2 PARALLEL_TO_SERIAL SELECT DISTINCT C0 C0,C1 C1 FROM :Q13049000 ORDER BY C0,C1
3 PARALLEL_TO_PARALLEL SELECT /*+ INDEX_RRS(A1 "CCMMT_UQ1")*/ A1."CDE" C0,A1."CA
4 PARALLEL_TO_SERIAL SELECT DISTINCT C0 C0,C1 C1 FROM :Q13050000 ORDER BY C0,C1
5 PARALLEL_TO_PARALLEL SELECT /*+ INDEX_RRS(A1 "CCMMT_UQ1")*/ A1."CDE" C0,A1."CA
Statistics
----------------------------------------------------------
0 recursive calls
33 db block gets
126566 consistent gets
129243 physical reads
0 redo size
18461368 bytes sent via SQL*Net to client
519785 bytes received via SQL*Net from client
47196 SQL*Net roundtrips to/from client
4 sorts (memory)
2 sorts (disk)
707924 rows processed
效果不错,Consistent gets 和 Physical Reads都下降了,同时只需要21s就返回了。但从查询计划看,用到了并行查询,因此会消耗更多的CPU。
在(ADT, CDE, CID )上创建索引,再次执行:
3、
SQL> select DISTINCT CDE, CID
2 from CCMMT
3 where ADT < sysdate - 180
4 minus
5 select DISTINCT CDE, CID
6 from CCMMT
7 where ADT >= sysdate - 180;
707924 rows selected.
Elapsed: 00:00:26.94
Execution Plan
----------------------------------------------------------
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=36018 Card=2794940 Bytes=111797600)
1 0 MINUS
2 1 SORT (UNIQUE) (Cost=18009 Card=2794940 Bytes=55898800)
3 2 INDEX (RANGE SCAN) OF 'CCMMT_IDX3' (NON-UNIQUE) (Cost=2 Card=2898455 Bytes=57969100)
4 1 SORT (UNIQUE) (Cost=18009 Card=2794940 Bytes=55898800)
5 4 INDEX (RANGE SCAN) OF 'CCMMT_IDX3' (NON-UNIQUE) (Cost=2 Card=2898455 Bytes=57969100)
Statistics
----------------------------------------------------------
0 recursive calls
118 db block gets
22565 consistent gets
31604 physical reads
0 redo size
18461368 bytes sent via SQL*Net to client
519785 bytes received via SQL*Net from client
47196 SQL*Net roundtrips to/from client
1 sorts (memory)
1 sorts (disk)
707924 rows processed
效果也比较理想,consistent gets和physical reads再次大大下降,返回时间和上面差不多,在一个数量级上,但是不再使用并行查询了。
用NOT Exists代替minus:
4、
SQL> select DISTINCT CDE, CID
2 from CCMMT a
3 where ADT < sysdate - 180
4 AND NOT EXISTS
5 (SELECT CDE, CID FROM
6 (select DISTINCT CDE, CID
7 from CCMMT
8 where ADT >= sysdate - 180) b
9 WHERE a.CDE = b.CDE
10 AND a.CID = b.CID);
707924 rows selected.
Elapsed: 00:10:35.70
Execution Plan
----------------------------------------------------------
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=600 Card=144923 Bytes=2898460)
1 0 SORT (UNIQUE) (Cost=600 Card=144923 Bytes=2898460)
2 1 INDEX (RANGE SCAN) OF 'CCMMT_IDX3' (NON-UNIQUE)(Cost=2 Card=144923 Bytes=2898460)
3 2 TABLE ACCESS (BY INDEX ROWID) OF 'CCMMT' (Cost=2 Card=1 Bytes=20)
4 3 INDEX (RANGE SCAN) OF 'CCMMT_TEMP_IDX' (NON-UNIQUE) (Cost=1 Card=9)
Statistics
----------------------------------------------------------
5 recursive calls
118 db block gets
40535587 consistent gets
3157604 physical reads
0 redo size
18461368 bytes sent via SQL*Net to client
519785 bytes received via SQL*Net from client
47196 SQL*Net roundtrips to/from client
2 sorts (memory)
1 sorts (disk)
707924 rows processed
FT! consistent gets和physical reads爆涨,10min才返回结果!
用Not In换掉Not Exists:
5、
SQL> select DISTINCT CDE, CID
2 from CCMMT a
3 where ADT < sysdate - 180
4 AND (CDE, CID) NOT IN
5 (select DISTINCT CDE, CID
6 from CCMMT
7 where ADT >= sysdate - 180);
707924 rows selected.
Elapsed: 00:01:00.70
Execution Plan
----------------------------------------------------------
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=36425 Card=1 Bytes=40)
1 0 SORT (UNIQUE NOSORT) (Cost=36425 Card=1 Bytes=40)
2 1 MERGE JOIN (ANTI) (Cost=36423 Card=1 Bytes=40)
3 2 SORT (JOIN) (Cost=18212 Card=2898455 Bytes=57969100)
4 3 INDEX (RANGE SCAN) OF 'CCMMT_IDX3' (NON-UNIQUE) (Cost=2 Card=2898455 Bytes=57969100)
5 2 SORT (UNIQUE) (Cost=18212 Card=2898455 Bytes=57969100)
6 5 INDEX (RANGE SCAN) OF 'CCMMT_IDX3' (NON-UNIQUE) (Cost=2 Card=2898455 Bytes=57969100)
Statistics
----------------------------------------------------------
0 recursive calls
419 db block gets
22565 consistent gets
98692 physical reads
0 redo size
18461368 bytes sent via SQL*Net to client
519785 bytes received via SQL*Net from client
47196 SQL*Net roundtrips to/from client
1 sorts (memory)
1 sorts (disk)
707924 rows processed
恩,consistent gets和建了索引时的minus方式一样,但是physical reads太大,返回时间太长---1min。同时用到了刚才建的索引。(呵呵,所以说,NOT EXISTS并不是什么情况下都比NOT IN更优啊)
在尝试用left join + is null代替not in:
6、
SQL> SELECT a.CDE, a.CID
2 FROM
3 (select DISTINCT CDE, CID
4 from CCMMT
5 where ADT < sysdate - 180) a,
6 (select DISTINCT CDE, CID
7 from CCMMT
8 where ADT >= sysdate - 180) b
9 WHERE a.CDE = b.CDE(+)
10 AND a.CID = b.CID(+)
11 AND b.CDE IS NULL;
707924 rows selected.
Elapsed: 00:00:25.46
Execution Plan
----------------------------------------------------------
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=54675 Card=2794940 Bytes=117387480)
1 0 FILTER
2 1 MERGE JOIN (OUTER)
3 2 VIEW (Cost=18009 Card=2794940 Bytes=58693740)
4 3 SORT (UNIQUE) (Cost=18009 Card=2794940 Bytes=55898800)
5 4 INDEX (RANGE SCAN) OF 'CCMMT_IDX3' (NON-UNIQUE) (Cost=2 Card=2898455 Bytes=57969100)
6 2 SORT (JOIN) (Cost=36667 Card=2794940 Bytes=58693740)
7 6 VIEW (Cost=18009 Card=2794940 Bytes=58693740)
8 7 SORT (UNIQUE) (Cost=18009 Card=2794940 Bytes=55898800)
9 8 INDEX (RANGE SCAN) OF 'CCMMT_IDX3' (NON-UNIQUE) (Cost=2 Card=2898455 Bytes=57969100)
Statistics
----------------------------------------------------------
10 recursive calls
118 db block gets
22569 consistent gets
31300 physical reads
0 redo size
18461368 bytes sent via SQL*Net to client
519785 bytes received via SQL*Net from client
47196 SQL*Net roundtrips to/from client
6 sorts (memory)
1 sorts (disk)
707924 rows processed
效果不错,和有索引时使用minus在同一数量级上。
总结,以上几种方式中,效果最好的应该是第3种和第6种,buffer gets、磁盘IO和CPU消耗都比较少,返回时间大大减少,但是需要新建一个索引,消耗更多磁盘空间,并存在影响其它语句的正常查询计划的风险。而第2种方式应该是次好的。在返回时间上,和上面两种差不多,不需要新的索引,但是会消耗更多的内存、磁盘和CPU资源。
出于综合考虑,采用了第2种方式对生产库进行了优化。
(以上例子中的对象名进行了替换,其他都是原版)
对Group By 语句的一次优化过程相关推荐
- mysql group by 天_MySQL group by语句如何优化
在MySQL中,新建立一张表,该表有三个字段,分别是id,a,b,插入1000条每个字段都相等的记录,如下: mysql> show create table t1G ************* ...
- 优化group by 语句
优化group by 语句 由于GROUP BY 实际上也同样会进行排序操作,而且与ORDER BY 相比,GROUP BY 主要只是多了排序之后的分组操作. 当然,如果在分组的时候还使用了其他的一些 ...
- 37 | MySQL的内部临时表使用场景?(Group by语句使用注意事项)
一.前言 在执行语句时候,记得多"食用"explian看看语句性能如何? create table t1(id int primary key, a int, b int, ind ...
- SQL GROUP BY 语句
合计函数 (比如 SUM) 常常需要添加 GROUP BY 语句. GROUP BY 语句 GROUP BY 语句用于结合合计函数,根据一个或多个列对结果集进行分组. SQL GROUP BY 语法 ...
- uwp连接mysql数据库_mysql 8.0 新版本出现group by 语句不兼容问题
mysql 新版本出现group by 语句不兼容问题 1. 具体出错提示: [Err] 1055 - Expression #1 of ORDER BY clause is not in GROUP ...
- GROUP BY 语句
GROUP BY 语句用于结合聚合函数,根据一个或多个列对结果集进行分组 GROUP BY 语法 SELECT column_name, aggregate_function(column_name) ...
- MySQL GROUP BY 语句
GROUP BY 语句根据一个或多个列对结果集进行分组. 在分组的列上我们可以使用 COUNT, SUM, AVG,等函数. GROUP BY 语法 SELECT column_name, funct ...
- 《零基础》MySQL GROUP BY 语句(十九)
GROUP BY 语句根据一个或多个列对结果集进行分组. 在分组的列上我们可以使用 COUNT, SUM, AVG,等函数. GROUP BY 语法 SELECT column_name, funct ...
- MySQL(21)--- GROUP BY 语句
GROUP BY 语句根据一个或多个列对结果集进行分组. 在分组的列上我们可以使用 COUNT, SUM, AVG,等函数. GROUP BY 语法 SELECT column_name, funct ...
最新文章
- 皮一皮:防狼泳衣...
- SqlSugar最容易使用的ORM
- matlab 计算指北角,用MATLAB如何计算出矩形区域内的最大值?
- Windows10关闭占用某一端口号的进程
- 【Mark工具】一些好用的图片标注工具
- 久其报表软件基本操作指引
- 数学分析教程(科大)——2.8笔记+习题
- typedef 定义结构体说明
- 奥城大学计算机专业,美国提供研究生双录取的大学
- 计算机的格式刷,“excle怎样取消格式刷“电脑上格式刷怎么用excel2000
- Symbol数据类型
- mac怎么显示服务器中隐藏文件,mac怎么显示隐藏文件夹-mac显示隐藏文件命令与使用教程 - 河东软件园...
- 2021年HSP律所代理品牌侵权案件合集,赶紧查看避免踩坑
- python去除pdf水印_聊聊 Python 操作PDF的几种方法(合并、拆分、水印、加密)
- 蓝牙a2dp协议源码分析
- (一)公主连结游戏拆解
- 计算机系统瘫痪重装系统文件怎么保存,我的电脑已经瘫痪,进不去了,要重做系统,现在应该怎么把C盘备份呢? 爱问知识人...
- mysql反删除恢复软件下载_MySQL Recovery(MySQL恢复软件)下载 v4.1官方版-下载啦
- 排产易!APS系统如何选型?(上)
- preall点云粗对齐作为matlab函数,pca和普氏分析法都有函数,主成分也有函数
热门文章
- 针对B2B平台的接口自动化测试系统
- mysqld服务启动失败, Failed to restart mysqld.service: Unit not found.
- synchronized的理解
- thinkphp传递参数
- 分割视图控制器(UISplitViewController)
- 关于继承方式和访问权限
- 读取笔记本的摄像头的原始yuv数据,通过libav(ffmpeg编码)
- ioctl函数_Linux字符设备驱动之实现ioctl文件操作
- 实时计算 Flink 版总体介绍
- Flink 在有赞的实践和应用