关于mysql innodb count(*)速度慢的解决办法
更新时间：2012年12月16日 12:35:32 作者：
innodb引擎在统计方面和myisam是不同的，Myisam内置了一个计数器，所以在使用 select count(*) from table 的时候，直接可以从计数器中取出数据。而innodb必须全表扫描一次方能得到总的数量
innodb引擎在统计方面和myisam是不同的，Myisam内置了一个计数器，所以在使用 select count(*) from table 的时候，直接可以从计数器中取出数据。而innodb必须全表扫描一次方能得到总的数量。要初步解决这个问题，需要做不同于myisam的一些工作：
1、使用第二索引（一般不使用主键索引），并且添加where条件，如：
select count（*） from product where comp_id>=0 ;
show index from product ;
id primary key
comp_id index
2、如果只需要粗略统计的话也可使用
show status from product; 来得到大约值
这种方法可在数据分页中使用！
3、使用外部计数器，比如建立一个触发器来计数或者在程序上使用缓存方式定时计数，缺陷是这些方法会额外消耗一些资源！
参考资料：
mysql高性能：http://www.mysqlperformanceblog.com/2006/12/01/count-for-innodb-tables/
mysql DBA:http://imysql.cn/2008_06_24_speedup_innodb_count
COUNT(*) for Innodb Tables
I guess note number one about MyISAM to Innodb migration is warning what Innodb is very slow in COUNT(*) queries. The part which I often however see omitted is fact it only applies to COUNT(*) queries without WHERE clause.
So if you have query like SELECT COUNT(*) FROM USER It will be much faster for MyISAM (MEMORY and some others) tables because they would simply read number of rows in the table from stored value. Innodb will however need to perform full table scan or full index scan because it does not have such counter, it also can't be solved by simple singe counter for Innodb tables as different transactions may see different number of rows in the table.
If you have query like SELECT COUNT(*) FROM IMAGE WHERE USER_ID=5 this query will be executed same way both for MyISAM and Innodb tables by performing index rage scan. This can be faster or slower both for MyISAM and Innodb depending on various conditions.
In real applications there are much more queries of second type rather than first type so it is typically not as bad problem as it may look. Most typically count of rows is needed by admin tools which may show it in table statistics, it may also be used in application stats to show something like “We have 123.345 users which have uploaded 1.344.656 images” but these are normally easy to remove.
So remember Innodb is not slow for ALL COUNT(*) queries but only for very specific case of COUNT(*) query without WHERE clause. It does not mean I would not like to see it fixed though, it is pretty annoying.
转自：http://www.sphinxsearch.org/archives/89
1、使用第二索引（一般不使用主键索引），并且添加where条件，如：
复制代码 代码如下:
select count（*） from product where comp_id>=0 ;
show index from product ;
id primary key
comp_id index
2、如果只需要粗略统计的话也可使用
show status from product; 来得到大约值
这种方法可在数据分页中使用！
3、使用外部计数器，比如建立一个触发器来计数或者在程序上使用缓存方式定时计数，缺陷是这些方法会额外消耗一些资源！
参考资料：
mysql高性能：http://www.mysqlperformanceblog.com/2006/12/01/count-for-innodb-tables/
mysql DBA:http://imysql.cn/2008_06_24_speedup_innodb_count
COUNT(*) for Innodb Tables
I guess note number one about MyISAM to Innodb migration is warning what Innodb is very slow in COUNT(*) queries. The part which I often however see omitted is fact it only applies to COUNT(*) queries without WHERE clause.
So if you have query like SELECT COUNT(*) FROM USER It will be much faster for MyISAM (MEMORY and some others) tables because they would simply read number of rows in the table from stored value. Innodb will however need to perform full table scan or full index scan because it does not have such counter, it also can't be solved by simple singe counter for Innodb tables as different transactions may see different number of rows in the table.
If you have query like SELECT COUNT(*) FROM IMAGE WHERE USER_ID=5 this query will be executed same way both for MyISAM and Innodb tables by performing index rage scan. This can be faster or slower both for MyISAM and Innodb depending on various conditions.
In real applications there are much more queries of second type rather than first type so it is typically not as bad problem as it may look. Most typically count of rows is needed by admin tools which may show it in table statistics, it may also be used in application stats to show something like “We have 123.345 users which have uploaded 1.344.656 images” but these are normally easy to remove.
So remember Innodb is not slow for ALL COUNT(*) queries but only for very specific case of COUNT(*) query without WHERE clause. It does not mean I would not like to see it fixed though, it is pretty annoying.
转自：http://www.sphinxsearch.org/archives/89
相关文章
最新Navicat 15 for MySQL破解+教程 正确破解步骤
Navicat for MySQL是一个针对MySQL数据库而开发的第三方mysql管理工具，该软件可以用于 MySQL 数据库服务器版本 3.21 或以上的和 MariaDB 5.1 或以上，这篇文章主要介绍了最新Navicat 15 for MySQL破解+教程 正确破解步骤,需要的朋友可以参考下2023-04-04
这篇文章主要介绍了深入解析MySQL的窗口函数,窗口可以理解为记录集合，窗口函数就是在满足某种条件的记录集合上执行的特殊函数,即：应用在窗口内的函数,需要的朋友可以参考下2023-07-07
本文详细介绍了在SQL中进行多表查询的技术,包括笛卡尔积、自连接、子查询、内连接和外连接等,文章还解释了union和unionall的区别,以及如何在from子句中使用子查询,这些技术对于处理复杂的数据库查询非常重要,可以有效地从不同表中提取和组合数据,需要的朋友可以参考下2024-10-10
这篇文章主要介绍了MySQL数据库之数据表操作DDL数据定义语言，文章围绕主题展开详细的内容介绍，具有一定的参考价值，需要的小伙伴可以参考一下2022-08-08
这篇文章主要介绍了CentOS7 通过YUM安装MySQL5.7的步骤详解，本文给大家介绍的非常详细，具有一定的参考借鉴价值,需要的朋友可以参考下2020-01-01
这篇文章主要介绍了MySQL INNER JOIN 的底层实现原理,INNER JOIN的工作分为筛选和连接两个步骤，连接时可以使用多种算法，通过本文，我们深入了解了MySQL中INNER JOIN的底层实现原理，需要的朋友可以参考下2023-06-06
下面小编就为大家带来一篇浅谈MySQL中group_concat()函数的排序方法。小编觉得挺不错的，现在就分享给大家，也给大家做个参考。一起跟随小编过来看看吧2016-12-12
这篇文章主要介绍了MySQL的存储函数与存储过程的区别,本文给大家介绍的非常详细，对大家的学习或工作具有一定的参考借鉴价值，需要的朋友可以参考下2022-04-04
随着管理mysql服务器越来越多，同样的mysql>的提示符有可能会让你输入错误的命令到错误的数据库，这时候需要巧用mysql的提示符，这是我的提示符root@localhost(mysql) 08:55:21> 用prompt命令实现(适用于windows和linux环境)2009-08-08
如何使用myisamchk和mysqlcheck工具快速修复损坏的MySQL数据库文件
有时候数据库突然就坏了很郁闷，用mysqlcheck.exe可以修复受损数据库2020-01-01
最新评论