zoukankan      html  css  js  c++  java
  • MySQL数据库in 太多不走索引案例

    https://dev.mysql.com/doc/refman/5.7/en/range-optimization.html

    Limiting Memory Use for Range Optimization

    To control the memory available to the range optimizer, use the range_optimizer_max_mem_size system variable:

    • A value of 0 means no limit.”

    • With a value greater than 0, the optimizer tracks the memory consumed when considering the range access method. If the specified limit is about to be exceeded, the range access method is abandoned and other methods, including a full table scan, are considered instead. This could be less optimal. If this happens, the following warning occurs (where N is the current range_optimizer_max_mem_size value):

    同样的SQL语句,in 几百个。在一台实例上走索引,在另一个实例上不走索引,第一感觉是和eq_range_index_dive_limit 之类的参数,调了几次之后无法复现问题,在看帮助文档时才注意到 range_optimizer_max_mem_size 参数也会引起全表扫描。

    问题复现如下:

    mysql> show create table t1;
    +-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
    | Table | Create Table                                                                                                                                                                                                                                                   |
    +-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
    | t1    | CREATE TABLE `t1` (
      `id` int(11) NOT NULL AUTO_INCREMENT,
      `od` int(11) DEFAULT NULL,
      `name` varchar(200) DEFAULT NULL,
      PRIMARY KEY (`id`),
      UNIQUE KEY `od` (`od`),
      KEY `idx_name` (`name`)
    ) ENGINE=InnoDB AUTO_INCREMENT=101 DEFAULT CHARSET=utf8 |
    +-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
    1 row in set (0.00 sec)
    
    
    mysql> select * from t1;
    +-----+------+------+
    | id  | od   | name |
    +-----+------+------+
    |   1 |    1 | a    |
    |   2 |    2 | b    |
    |   3 |    3 | c    |
    |   4 |    4 | d    |
    | 100 |  100 | f    |
    +-----+------+------+
    5 rows in set (0.00 sec)
    
    mysql> show variables like 'range_optimizer_max_mem_size';
    +------------------------------+---------+
    | Variable_name                | Value   |
    +------------------------------+---------+
    | range_optimizer_max_mem_size | 8388608 |
    +------------------------------+---------+
    1 row in set (0.00 sec)
    
    mysql> explain select * from t1 where id in(1,3,5);
    +----+-------------+-------+------------+-------+---------------+---------+---------+------+------+----------+-------------+
    | id | select_type | table | partitions | type  | possible_keys | key     | key_len | ref  | rows | filtered | Extra       |
    +----+-------------+-------+------------+-------+---------------+---------+---------+------+------+----------+-------------+
    |  1 | SIMPLE      | t1    | NULL       | range | PRIMARY       | PRIMARY | 4       | NULL |    3 |   100.00 | Using where |
    +----+-------------+-------+------------+-------+---------------+---------+---------+------+------+----------+-------------+
    1 row in set, 1 warning (0.00 sec)
    
    
    mysql> set range_optimizer_max_mem_size=1;
    Query OK, 0 rows affected (0.00 sec)
    
    mysql> 
    mysql> explain select * from t1 where id in(1,3,5);
    +----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+-------------+
    | id | select_type | table | partitions | type | possible_keys | key  | key_len | ref  | rows | filtered | Extra       |
    +----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+-------------+
    |  1 | SIMPLE      | t1    | NULL       | ALL  | PRIMARY       | NULL | NULL    | NULL |    6 |    50.00 | Using where |
    +----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+-------------+
    1 row in set, 2 warnings (0.00 sec)
  • 相关阅读:
    icomet研究
    python使用ssdb的队列,用于替换canal+rabbitmq
    最近关于mysql的造型,binlog使用,以及阿里云上线数据处理错误导致被处罚的思考
    删除一个存在的RabbitMQ队列
    检查Rabbitmq中队列及消息个数,还有清空的方法
    Mysql在master上查看有哪些slave
    查看Linux端口的占用及连接情况
    Kettle根据时间戳同步数据实现
    kettle的下载、安装和初步使用(windows平台下)(图文详解)
    golang学习 ----获取URL
  • 原文地址:https://www.cnblogs.com/nanxiang/p/15133394.html
Copyright © 2011-2022 走看看