【问题标题】:Probably bad index, full table scan可能是坏索引,全表扫描
【发布时间】:2016-06-29 14:08:07
【问题描述】:

你能帮我索引我的表吗?

问题是我索引了我的表,但我的解释中仍然有“全表扫描”

这是我的(工作)查询,但在大表上它可能会很慢,而且我不知道如何更改它

EXPLAIN select * from  stats_clicked s
join visitor v on s.visitor_id=v.id

ps。 index3 - 当访问者=1 刷新 id=5 的页面时,我不想多次取值 (1,5)

CREATE TABLE `visitor` (
   `id` int(11) NOT NULL AUTO_INCREMENT,
   `visited_time` int(11) DEFAULT NULL,
   PRIMARY KEY (`id`)
 ) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8;

CREATE TABLE `stats_clicked` (
   `id` int(11) NOT NULL AUTO_INCREMENT,
   `visitor_id` int(11) NOT NULL,
   `page_clicked_id` int(11) DEFAULT NULL,
   PRIMARY KEY (`id`),
   UNIQUE KEY `index3` (`visitor_id`,`page_clicked_id`),
   KEY `index1` (`visitor_id`)
 ) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8;


insert into visitor (`visited_time`) values
(1467122944),(1467122944),(1467122944),
(1467122944),(1467122944),(1467122944),
(1467122944),(1467122944),(1467122944),
(1467122944),(1467122944),(1467122944),
(1467122944),(1467122944),(1467122944);

insert into `stats_clicked` ( `visitor_id`,`page_clicked_id`) values
(1,47),(2,24),(3,83),(3,8),(3,85),(3,88),(4,57),
(5,2),(6,1),(7,28),(8,83),(9,11),(9,16),(9,1),(10,17),
(11,70),(12,73),(13,97),(14,57),(15,30),(15,2),(15,22);

【问题讨论】:

  • 你的错误是什么?你不能做什么?
  • 如果您希望 (visitor_id, page_clicked_id) 是唯一的并且不接受 visitor_id = 1 和 page_clicked_id =5 多次
  • 问题是我索引了我的表,但我的解释中仍然有“全表扫描”
  • 不确定...但也许您需要在表stats_clicked 中的visitor_id 上添加FOREIGN KEY 以使该列唯一,并使join 更快,因为这是您唯一的条件'在join中使用。
  • 也许这适用,“索引列的 ON 或 WHERE 子句中没有可用的限制。”在dev.mysql.com/doc/refman/5.7/en/how-to-avoid-table-scan.html

标签: mysql indexing full-table-scan


【解决方案1】:

如果我执行你上面所做的,我会得到

EXPLAIN select * from  stats_clicked s 
join visitor v on s.visitor_id=v.id 
+----+-------------+-------+------+---------------+--------+---------+--------------------+------+-------------+
| id | select_type | table | type | possible_keys | key    | key_len | ref                | rows | Extra       |
+----+-------------+-------+------+---------------+--------+---------+--------------------+------+-------------+
|  1 | SIMPLE      | v     | ALL  | PRIMARY       | NULL   | NULL    | NULL               |   15 | NULL        |
|  1 | SIMPLE      | s     | ref  | index3,index1 | index3 | 4       | so_gibberish2.v.id |    1 | Using index |
+----+-------------+-------+------+---------------+--------+---------+--------------------+------+-------------+

但是,如果我截断然后执行以下大量数据加载(最终超过 100K 行):

truncate table visitor;

insert into visitor (`visited_time`) values
(1467122944),(1467122944),(1467122944),
(1467122944),(1467122944),(1467122944),
(1467122944),(1467122944),(1467122944),
(1467122944),(1467122944),(1467122944),
(1467122944),(1467122944),(1467122944);

insert into visitor (`visited_time`) values
(1467122945),(1467122945),(1467122945),
(1467122945),(1467122945),(1467122945),
(1467122945),(1467122945),(1467122945),
(1467122945),(1467122945),(1467122945),
(1467122945),(1467122945),(1467122945),


insert into visitor (`visited_time`) values
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946);

insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;

select count(*) from visitor;
-- 104448 rows

这会导致不是表扫描:

EXPLAIN select * from  stats_clicked s 
join visitor v on s.visitor_id=v.id; 

+----+-------------+-------+--------+---------------+---------+---------+----------------------------+------+-------------+
| id | select_type | table | type   | possible_keys | key     | key_len | ref                        | rows | Extra       |
+----+-------------+-------+--------+---------------+---------+---------+----------------------------+------+-------------+
|  1 | SIMPLE      | s     | index  | index3,index1 | index3  | 9       | NULL                       |   22 | Using index |
|  1 | SIMPLE      | v     | eq_ref | PRIMARY       | PRIMARY | 4       | so_gibberish2.s.visitor_id |    1 | NULL        |
+----+-------------+-------+--------+---------------+---------+---------+----------------------------+------+-------------+

原因在手册页How MySQL Uses Indexes中列出:

索引更少 对于小表或报告的大表的查询很重要 查询处理大部分或所有行。当查询需要访问时 大多数行,按顺序阅读比通读要快 一个索引。顺序读取最小化磁盘寻道,即使不是所有的 查询需要行。

上面列出的原因。在您的问题示例中,您的行数太少,无法使用索引。因此,db 引擎选择了其所谓(并且可能)更快的方式,即不使用小表上的索引。

【讨论】:

  • 当然,这不是“表扫描”,而是“索引扫描”。
  • 我表明人们应该相信 explain 有足够的数据,而不是 15 次插入。
【解决方案2】:

stats_clicked 不需要id。事实上,它的存在减慢了对该表的所有可能查询。 More details.

【讨论】:

    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2016-11-24
    • 2013-10-01
    • 2011-03-12
    • 1970-01-01
    • 2020-01-10
    相关资源
    最近更新 更多