Would you consider a switch to MySQLTuner 2 particularly since the original developer said that he doesn't have the time to maintain V1 anymore back in January 2010?

Seems some interesting developments are being put into v2.

Thanks

dayo: There is a typo in the link posted, should be: https://launchpad.net/mysqltuner - would be interested in seeing the project continue. Might be worth reading Major Hayden's Blog: http://blog.mysqltuner.com/2010/01/sear ... /#comments - some folks seem to have issue with its future under Pythian (?) - its gone quiet the past couple of months though.

The output of the 2.1 (Sheeri Cabral) version is different from 1.1.1 (Major Hayden) version, although the same info is there, no recommendations are made - which is the key to its popularity. Anyone else taken a look?

My biggest issue with current (1.1.1) version is InnoDB tables no longer support optimize (using recreate + analyze instead) so the MySQL Tuner report: "Run OPTIMIZE TABLE to defragment tables for better performance" is misleading.

Probably best to stick with the 1.x branch when all is said and done.

Following an earlier post where I mentioned:
I discovered a simple solution was to alter line 473 of mysqltuner from:
To:
Essentially removing InnoDB tables from the fragmentation check. No doubt there is a better way... but the stuff I need to focus on uses MyISAM and this might be useful to others.