Bug #21712 description how analyze works on innodb tables
Submitted: 18 Aug 2006 8:45 Modified: 7 Sep 2006 0:56
Reporter: Oli Sennhauser Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S4 (Feature request)
Version:all OS:n.a.
Assigned to: Paul DuBois CPU Architecture:Any

[18 Aug 2006 8:45] Oli Sennhauser
Description:
Found some more technical details how analyze table works on innodb tables.

How to repeat:
n.a.

Suggested fix:
On http://www.mysqlperformanceblog.com/category/innodb/ I found that:

Innodb statistics  - Unlike MyISAM Innodb does not store index cardinality in tables, instead it computes them on first table access after startup. This may take significant time if you have very large number of tables (Some users have hundreds of thousands of tables per database host). This one is pretty much part of cold start problems but I wanted to point out it separately. To warmup this data you might run select 1 from _table_ limit 1 for each table or any other statement - it is table open which is important.

I think it is worth to mention it e.g. here: http://dev.mysql.com/doc/refman/5.0/en/innodb-restrictions.html

But I think this is the wrong place anyway!
[7 Sep 2006 0:56] Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

Added a note to http://dev.mysql.com/doc/refman/5.0/en/innodb-tuning.html.