Hack MySQL Blog

The Guide To Understanding mysqlreport has been updated. As many people have noticed, since mysqlreport v3.2, Key Write and Read ratio went away, replaced by Write and Read hit percentage. I figured that “99.87%” was more intuitive than “0.0013″.

mysqlreport v3.2 has been released. Mark Leith’s post, Aggregating SHOW STATUS Output, reminded me that a user had asked me a few months ago to do this for mysqlreport. I forgot until Mark’s post.

I have finished implementing this feature with mysqlreport. The new version has three new command line options: –relative (-r), –report-count (-c), and –detach. All of these are explained in the doc. This feature required substantial alterations to the script, so please tell me if anything doesn’t work.

Yesterday I released mysqlreport v3.1. No large changes:

• Added support for table_open_cache system var (MySQL 5.1.3+).
• Removed default assignments for $mycnf{’host’}, $mycnf{’port’}, and $mycnf{’socket’}.
• Connecting to MySQL now tries socket if one is given and actually a socket, else TCP/IP host if one is given, else generic “host=localhost” which relies on the MySQL client lib to do something useful.
• Updated help for clarity.
• Fixed bug: spelled “fsync” wrong.

I also updated The Guide To Understanding mysqlreport to include InnoDB reports and the mysqlreport documentation.

It’s strange what articles on one’s site become “popular.” I wrote Non-technical Guide to Isolating Slow MySQL Queries some time ago when I was an internal system admin at a data center. I wasn’t “customer-facing” but I still got requests from customers who wanted me to look at their MySQL server. Since that wasn’t my primary responsibility, I had to enlist their help to save me time. Hence, I wrote this article to help not-technically-inclined customers through the first few steps.

My webstats have shown this page to be hit more often than I would have expected. Consequently, I felt that I should update it, so I did.

mysqlreport v3.0a has been released which fixes a bug on line 93:

chomperc($mycnf{’pass’} = <STDIN>);

should be just

chomp($mycnf{’pass’} = <STDIN>);

Thanks to jeroen for pointing this out to me. This bug caused mysqlreport to die when using –pass to prompt for a password:

Undefined subroutine &main::chomperc called at mysqlreport line 93

In other news: thanks also to Aurimas for some technical clarifications in the mysqlreport Guide about temp tables.