mysqlsla: I’m going to create a hybrid between this and mk-log-parser. Whereas mysqlsla does some things that mk-log-parser doesn’t, mk-log-parser has a better, more maintainable code base. Furthermore, I’m currently working on other log handling code which will affect some future plans I had for mysqlsla such as grouping results and filtering by timestamp.

mysqlreport: Apparently, it’s “bug-free” because no one has reported a single problem with it in so long that I couldn’t even tell you when it was last released. Regardless, I have plans for this, too, such as better interaction with other scripts by decoupling the code, data and presentation further.

mysqlidxchk: This has needed serious work since its release which wasn’t possible for various “technical” reasons. But I can fix it now and make it better, more helpful.

In general, I’m also moving my entire code base to Google Code, too, since I’ll be re-using some Maatkit common modules in my own scripts. Plus, that will make it easier to track issues and changes for me and you.

• Fixed bug: incorrect checking of MySQL version caused mysqlreport to ignore InnoDB status values in some cases. Simplified version from 3 integers (major, minor, patch) to 1 (50024 = 5.0.24, 60001 = 6.0.1, etc.) for easier, more accurate version checking all around.
• Fixed potential bug: read_relative_infiles might have incorrectly divided infiles with multiple status value sets.
• Fixed bug: if wait_timeout was greater than –relative, mysqlreport would lose its connection while sleeping. Now the connection is closed and reopened for each live relative report collection.
• Infiles can now be given SHOW VARIABLES output (in addition to the old method of inserting values manually like: key_buffer_size=128M)
• Slow query time is beautified for microsecond, millisecond, and second resolution (format_u_time):
  0.000000 – 0.000999 = 0 – 999 µ
  0.001000 – 0.999999 = 1 ms – 999.999 ms
  1.000000 – n.nnnnnn = 1 s – n.nnnnn s
• Added a lot more debugging output.

• Fixed bug: InnoDB report values were wrong in relative reports because 13 InnoDB status values needed to be excluded from being made relative. (thanks Debbie)
• Changed InnoDB Buffer Pool Read ratio to Read hit %

The Guide to Understanding mysqlreport has been accordingly updated, too.

Changes in v3.4 are:

• Fixed bug: –relative infiles wouldn’t work unless the SHOW STATUS values were prefixed with a line matching: /Variable_name[\s|]+Value/. Now mysqlreport looks for Aborted_clients which should always be present. (thanks Debbie)
• Fixed formatting problem: Created Temp Table Size was too small for >99M
• Removed redundant %Total: column label from Slow line
• Added more debug info

• –all is now the default option and all the sub-report options like –dms, –sas, etc. have been removed. All reports that can be made are made automatically.
• Slow line now displays long_query_time and log_slow_queries
• Created Temp Table line now displays tmp_table_size
• The mysqlreport tgz and zip now extract into their own directory

The mysqlreport Documentation and The Guide To Understanding mysqlreport have been updated to reflect these changes.

]]> http://hackmysql.com/blog/2008/01/09/mysqlreport-v33-released/feed/ 0 http://hackmysql.com/blog/2007/06/26/guide-to-understanding-mysqlreport-updated/ http://hackmysql.com/blog/2007/06/26/guide-to-understanding-mysqlreport-updated/#comments Tue, 26 Jun 2007 23:14:54 +0000 Daniel Nichter http://hackmysql.com/wp/2007/06/26/guide-to-understanding-mysqlreport-updated/ 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″.
]]> http://hackmysql.com/blog/2007/06/26/guide-to-understanding-mysqlreport-updated/feed/ 0 http://hackmysql.com/blog/2007/05/26/mysqlreport-v32-released/ http://hackmysql.com/blog/2007/05/26/mysqlreport-v32-released/#comments Sat, 26 May 2007 21:41:50 +0000 Daniel Nichter http://hackmysql.com/wp/2007/05/26/mysqlreport-v32-released/ 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.

]]> http://hackmysql.com/blog/2007/05/26/mysqlreport-v32-released/feed/ 0 http://hackmysql.com/blog/2007/04/26/mysqlreport-v31-released/ http://hackmysql.com/blog/2007/04/26/mysqlreport-v31-released/#comments Thu, 26 Apr 2007 18:11:33 +0000 Daniel Nichter http://hackmysql.com/wp/2007/04/26/mysqlreport-v31-released/ 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.

]]> http://hackmysql.com/blog/2007/04/26/mysqlreport-v31-released/feed/ 0 http://hackmysql.com/blog/2007/04/11/updated-non-technical-guide-to-isolating-slow-mysql-queries/ http://hackmysql.com/blog/2007/04/11/updated-non-technical-guide-to-isolating-slow-mysql-queries/#comments Wed, 11 Apr 2007 21:43:49 +0000 Daniel Nichter http://hackmysql.com/wp/2007/04/11/updated-non-technical-guide-to-isolating-slow-mysql-queries/ 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.

]]> http://hackmysql.com/blog/2007/04/11/updated-non-technical-guide-to-isolating-slow-mysql-queries/feed/ 0 http://hackmysql.com/blog/2006/12/12/humility-four-days-later-mysqlreport-v30-fixed/ http://hackmysql.com/blog/2006/12/12/humility-four-days-later-mysqlreport-v30-fixed/#comments Tue, 12 Dec 2006 20:07:34 +0000 Daniel Nichter http://hackmysql.com/wp/?p=7 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.

]]> http://hackmysql.com/blog/2006/12/12/humility-four-days-later-mysqlreport-v30-fixed/feed/ 0