…upgrade of MySQL 4.1 running Innodb to MySQL 5.0 and doing oprofile analyzes we found very interesting issue of buf_get_latched_pages_number being …monitoring SHOW GLOBAL STATUS was run every couple of seconds being considered fast operation, as it is in MySQL 4.1 But why buf_get_latched_pages_number…

…buf_get_latched_pages_number from the standard build of mysqld. We may keep it in the UNIV_DEBUG build. Since SHOW INNODB STATUS\G prints all reserved latches…

Wow. The bug is still there even in the 5.1.23 InnoDB plugin. I have filed a bug — http://bugs.mysql.com/bug.php?id=36600. I have changed my builds to not call buf_get_latched_pages_number. Otherwise, the CPU gets saturated when SHOW STATUS commands are run.