(whatever happened to) MySQLTuner 2.0

MySQL DBAs are amazingly smart, they really impress me.

It’s really hard to figure out the right way to make MySQL perform better. Webservers and PHP have been improved to the point where mysql is often becoming the bottleneck.

I just finished porting over MySQL-Report into bbPress as a plugin. It was originally written by Daniel Nichter in Perl and then Munroe Richard converted it to PHP for Drupal, so I “borrowed” a great deal of his code to save some time. I am not that thrilled with the original code quality but I am feeling too lazy right now to rewrite it, and it works well enough.

Other analysis tools I use are tuner-primer and MySQLTuner (v1.2) The mysql summary from aspersa (now in the Percona Toolkit) is also somewhat helpful but not as useful.

For realtime tracking the updated version of MyTop from Mark Grennan (originally by Jeremy Zawodny) is somewhat useful on busy servers.

Now, does anyone know whatever happened to MySQLTuner 2.0 ?
Seems like they stopped working on it in 2010

Nice slideshow on it from Sheeri Cabral
http://technocation.org/files/doc/2010_10_mysqltuner.pdf

Video presentation with that slideshow

And check out this amazing addon for PHPMyAdmin that Tyron Madlener apparently wrote during the Google 2011 Summer of Code
http://tm.tyron.at/#pg41

Tyron Madlener's database monitor for PHPMyAdmin

I am trying to find it online, may have to email him.

I was really excited about MySQL 5.5 finally being pushed to the newest cpanel releases – until I noticed that MyIASM benchmarks for 5.5 are even slower than 5.1 – apparently 5.0 was even faster than 5.1 on MyISAM. Well at least when you only have a couple of cpu cores available – 5.5 admittedly starts pulling ahead when there are 4+ cores. But for the average VPS user, this is not a typical situation.

ps. Easy Security Tip for MySQL configuration
If you are only using mysql on a server for that one server and it’s not a dedicated server, you should turn off all TCP networking for mysql! Edit your `my.cnf` ASAP and add the line `skip-networking` (and restart mysql) Otherwise it’s listening for external connections instead of just local socket connections and it allows evil crackers to try to probe mysql. If you haven’t done this yet and see a high number of “Aborted Connects” you might be getting attacked over the network.