执行GROUP BY子句的最一般的方法:先扫描整个表,然后创建一个新的临时表,表中每个组的所有行应为连续的,最后使用该临时表来找到组

并应用聚集函数。在某些情况中,MySQL通过访问索引就可以得到结果,此类查询的 EXPLAIN 输出显示 Extra 列的值为 Using index for group-by。

一、松散索引扫描

The most efficient way to process GROUP BY is when an index is used to directly retrieve the grouping columns.

With this access method, MySQL uses the property of some index types that the keys are ordered (for example, BTREE).

This property enables use of lookup groups in an index without having to consider all keys in the index that satisfy all WHERE conditions.

This access method considers only a fraction of the keys in an index, so it is called a loose index scan.

When there is no WHERE clause, a loose index scan reads as many keys as the number of groups, which may be a much smaller number than that of all keys.

If the WHERE clause contains range predicates ,  a loose index scan looks up the first key of each group that satisfies the range conditions,

and again reads the least possible number of keys. This is possible under the following conditions:

  • The query is over a single table.

  • The GROUP BY names only columns that form a leftmost prefix of the index and no other columns.

(If, instead of GROUP BY, the query has a DISTINCT clause, all distinct attributes refer to columns that form a leftmost prefix of the index.)

For example, if a table t1 has an index on (c1,c2,c3),

loose index scan is applicable if the query has GROUP BY c1, c2,.

It is not applicable if the query has GROUP BY c2, c3 (the columns are not a leftmost prefix) or GROUP BY c1, c2, c4 (c4 is not in the index).

  • The only aggregate functions used in the select list (if any) are MIN() and MAX(), and all of them refer to the same column. The column must be in the index and must immediately follow the columns in the GROUP BY.

  • Any other parts of the index than those from the GROUP BY referenced in the query must be constants (that is, they must be referenced in equalities with constants), except for the argument of MIN() or MAX() functions.

  • For columns in the index, full column values must be indexed, not just a prefix. For example, with c1 VARCHAR(20), INDEX (c1(10)), the index cannot be used for loose index scan.

mysql5.7示例如下:

CREATE TABLE `sm_wechat_binding` (
`id` bigint(20) NOT NULL,
`company_id` bigint(20) DEFAULT NULL,
`date_created` datetime NOT NULL,
`is_big_account` bit(1) NOT NULL,
`last_updated` datetime NOT NULL,
`open_id` varchar(64) NOT NULL,
`phone` varchar(14) DEFAULT NULL,
`deleted` datetime DEFAULT NULL,
`imported` datetime DEFAULT NULL,
`client_id` bigint(20) DEFAULT NULL,
PRIMARY KEY (`id`),
KEY `company_id_idx` (`company_id`),
KEY `openid_phone_index` (`open_id`,`phone`),
CONSTRAINT `FK_f95swnll9d3myf1pl7o5cxtws` FOREIGN KEY (`company_id`) REFERENCES `sm_company` (`company_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4

mysql> EXPLAIN SELECT distinct company_id FROM sm_wechat_binding;
+----+-------------+-------------------+-------+----------------+----------------+---------+------+------+--------------------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+-------------------+-------+----------------+----------------+---------+------+------+--------------------------+
| 1 | SIMPLE | sm_wechat_binding | range | company_id_idx | company_id_idx | 9 | NULL | 699 | Using index for group-by |
+----+-------------+-------------------+-------+----------------+----------------+---------+------+------+--------------------------+
1 row in set (0.02 sec) mysql> EXPLAIN SELECT COUNT( company_id) FROM sm_wechat_binding GROUP BY company_id;
+----+-------------+-------------------+-------+----------------+----------------+---------+------+-------+-------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+-------------------+-------+----------------+----------------+---------+------+-------+-------------+
| 1 | SIMPLE | sm_wechat_binding | index | company_id_idx | company_id_idx | 9 | NULL | 39130 | Using index |
+----+-------------+-------------------+-------+----------------+----------------+---------+------+-------+-------------+
1 row in set (0.00 sec) mysql> EXPLAIN SELECT COUNT(distinct company_id) FROM sm_wechat_binding GROUP BY company_id;
+----+-------------+-------------------+-------+----------------+----------------+---------+------+------+--------------------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+-------------------+-------+----------------+----------------+---------+------+------+--------------------------+
| 1 | SIMPLE | sm_wechat_binding | range | company_id_idx | company_id_idx | 9 | NULL | 699 | Using index for group-by |
+----+-------------+-------------------+-------+----------------+----------------+---------+------+------+--------------------------+
1 row in set (0.00 sec) mysql> EXPLAIN SELECT COUNT(distinct company_id) as num, company_id FROM sm_wechat_binding GROUP BY company_id;
+----+-------------+-------------------+-------+----------------+----------------+---------+------+------+--------------------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+-------------------+-------+----------------+----------------+---------+------+------+--------------------------+
| 1 | SIMPLE | sm_wechat_binding | range | company_id_idx | company_id_idx | 9 | NULL | 699 | Using index for group-by |
+----+-------------+-------------------+-------+----------------+----------------+---------+------+------+--------------------------+
1 row in set (0.00 sec) mysql> EXPLAIN SELECT max(company_id), min(company_id) FROM sm_wechat_binding force index(company_id_idx);
+----+-------------+-------+------+---------------+------+---------+------+------+------------------------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+-------+------+---------------+------+---------+------+------+------------------------------+
| 1 | SIMPLE | NULL | NULL | NULL | NULL | NULL | NULL | NULL | Select tables optimized away |
+----+-------------+-------+------+---------------+------+---------+------+------+------------------------------+
1 row in set (0.01 sec)

示例二

mysql> CREATE TABLE `loose_index_scan` (
->
-> `c1` int(11) DEFAULT NULL,
-> `c2` int(11) DEFAULT NULL,
-> `c3` int(11) DEFAULT NULL,
-> `c4` int(11) DEFAULT NULL,
-> KEY `idx_g` (`c1`,`c2`,`c3`)
-> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
Query OK, 0 rows affected (0.90 sec) mysql>
mysql>
mysql> explain select c1,c2 from loose_index_scan group by c1,c2;
+----+-------------+------------------+-------+---------------+-------+---------+------+------+-------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+------------------+-------+---------------+-------+---------+------+------+-------------+
| 1 | SIMPLE | loose_index_scan | index | idx_g | idx_g | 15 | NULL | 1 | Using index |
+----+-------------+------------------+-------+---------------+-------+---------+------+------+-------------+
1 row in set (0.06 sec) mysql>
mysql>
mysql> EXPLAIN SELECT COUNT(DISTINCT c1) FROM loose_index_scan GROUP BY c1;
+----+-------------+------------------+-------+---------------+-------+---------+------+------+-------------------------------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+------------------+-------+---------------+-------+---------+------+------+-------------------------------------+
| 1 | SIMPLE | loose_index_scan | range | idx_g | idx_g | 5 | NULL | 2 | Using index for group-by (scanning) |
+----+-------------+------------------+-------+---------------+-------+---------+------+------+-------------------------------------+
1 row in set (0.02 sec)

参考:

官方文档:group-by-optimization

MySQL如何优化GROUP BY :松散索引扫描 VS 紧凑索引扫描的更多相关文章

  1. MySQL优化GROUP BY-松散索引扫描与紧凑索引扫描

    满足GROUP BY子句的最一般的方法是扫描整个表并创建一个新的临时表,表中每个组的所有行应为连续的,然后使用该临时表来找到组并应用累积函数(如果有).在某些情况中,MySQL能够做得更好,即通过索引 ...

  2. MySQL松散索引扫描与紧凑索引扫描

    什么是松散索引? 答:实际上就是当MySQL 完全利用索引扫描来实现GROUP BY 的时候,并不需要扫描所有满足条件的索引键即可完成操作得出结果. 要利用到松散索引扫描实现GROUP BY,需要至少 ...

  3. mysql数据库优化之 如何选择合适的列建立索引

    1. 在where 从句,group by 从句,order by 从句,on 从句中出现的列: 2. 索引字段越小越好: 3. 离散度大的列放到联合索引的前面:比如: select * from p ...

  4. MySQL架构优化实战系列1:数据类型与索引调优全解析

    一.数据类型优化 数据类型 整数   数字类型:整数和实数 tinyint(8).smallint(16).mediuint(24).int(32).bigint(64) 数字表示对应最大存储位数,如 ...

  5. MySql数据库 优化

    MySQL数据库优化方案 Mysql的优化,大体可以分为三部分:索引的优化,sql慢查询的优化,表的优化. 开启慢查询日志,可以让MySQL记录下查询超过指定时间的语句,通过定位分析性能的瓶颈,才能更 ...

  6. mysql 松散索引与紧凑索引扫描(引入数据结构)

    这一篇文章本来应该是放在 mysql 高性能日记中的,并且其优化程度并不高,但考虑到其特殊性和原理(索引结构也在这里稍微讲一下) 一,mysql 索引结构 (B.B+树) 要问到 mysql 的索引用 ...

  7. mysql 通过使用联全索引优化Group by查询

    /*SELECT count(*) FROM (*/ EXPLAIN SELECT st.id,st.Stu_name,tmpgt.time,tmpgt.goutong FROM jingjie_st ...

  8. MySQL性能优化——索引

    原文地址:http://blog.codinglabs.org/articles/theory-of-mysql-index.html InnoDB使用B+Tree作为索引结构 最左前缀原理与相关优化 ...

  9. mysql性能优化-慢查询分析、优化索引和配置

    一.优化概述 二.查询与索引优化分析 1性能瓶颈定位 Show命令 慢查询日志 explain分析查询 profiling分析查询 2索引及查询优化 三.配置优化 1)      max_connec ...

随机推荐

  1. Mac 常用命令介绍

    1.查看所有shell cat /etc/shells 2.查看当前使用的shell类型 $ echo $SHELL 3.

  2. Webpack 的 HtmlWebpackPlugin 如何控制某个 chunks 的 inject 位置?

    https://segmentfault.com/q/1010000006591131 通过修改 HtmlWebpackPlugin 源码实现了 修改后的配置: new HtmlWebpackPlug ...

  3. unity, 显示像素图,以及iOS下像素图变模糊解决办法

    在PS里画了个16x16像素的图: 在webplayer下Filter Mode选为Point,显示效果为: 在ios下显示效果为: 是由于iOS下会将图片压缩为pvr所致,想得到清晰的效果,需将Fo ...

  4. leetCode 30.Substring with Concatenation of All Words (words中全部子串相连) 解题思路和方法

    Substring with Concatenation of All Words You are given a string, s, and a list of words, words, tha ...

  5. 初识WatiN

    WatiN —— Web Application Testing In .Net 为什么会有WatiN? 给用户提供一个.Net平台下,将Web测试自动化的便捷途径. 如何通过WatiN来进行自动化测 ...

  6. 详解TCP建立连接全过程

    TCP是因特网中的传输层协议,使用三次握手协议建立连接,下面是TCP建立连接的全过程. 上图画出了TCP建立连接的过程.假定主机A是TCP客户端,B是服务端.最初两端的TCP进程都处于CLOSED状态 ...

  7. SecureCRT中的vim出现1H特殊字符

    问题原因:由于采用了UTF_8编码方式导致的. 解决方法:把字符编码改为:GB18030即可.如图:

  8. nc在centos7上的安装和简单使用

    下载 http://vault.centos.org/6.6/os/x86_64/Packages/nc-1.84-22.el6.x86_64.rpm     rpm -iUv nc-1.84-22. ...

  9. spring 第一篇(1-1):让java开发变得更简单(上)

    1.释放POJOS能量 传统开发中是如何束缚POJOS呢,如果你开发过java很长时间,那你一定有接触过EJB的开发.那时候开发一个小小的功能都要扩展框架的类或者实现其接口.所以你很容易在早期的Str ...

  10. Java并发编程(九)安全发布

    之前讨论是如何将对象封闭在线程之中,这样可以减少一些并发带来的同步和可见性问题.但是在有些时候,我们希望在多个线程间共享对象,此时必须确保安全地进行共享. [不安全发布的示例] 可见性问题:其他线程看 ...