Have you tried MySQLTuner yet? It's free and it makes optimizing your MySQL server easier than ever!

I’ve revamped a few of the recommendations in MySQLTuner, and revision 19 is now available tonight! Here’s the main changes:

* Adjusted infoprint to use asterisks (cosmetic)
* Per-thread/global buffer counts are now displayed
* Key buffer increases are only recommended if the buffer is smaller than total indexes and hit rate is < 95%
* Dropped max_seeks_for_key checks
* Temporary table size increases are not recommended over 256M
* Aborted connection calculation and recommendation adjustments

You can download the latest copy on the MySQLTuner page, and you can get diffs for the new version as well.

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google
  • Reddit
  • Slashdot
  • StumbleUpon
  • Technorati
  • TwitThis
4 Responses to “MySQLTuner Revision 19 is available”
  1. Thanks, this is awesome!

  2. I’m glad you like it! :-) Let me know if you have any suggestions for updates.

  3. This script is handy for a quick check on the health of a mysql instance. I modified the script to skip suggesting turning on concurrent inserts for SMP systems. Also I added a check to determine whether the innodb buffer and the innodb aditional memory pool ((nnodb buffer / 20) + whatever to get divisible by 16).

    I am curious why the 85% threshold for MySQL memory usage?

  4. I use the 85% threshold as I’ve found it to be a good average for most shared hosting environments. However, if the server is a dedicated MySQL server, the threshold could be increased to 90 or 95% of system memory. For servers running web applications that use a lot of memory, like Java or Ruby on Rails, the threshold may need to be lowered to allow for better stability of the whole system.

Leave a Reply

You must be logged in to post a comment. Login »