MySQLTuner v1.1.0 released

The first MySQLTuner release of 2009 is now available! You can download v1.1.0 directly or clone it from github. The full changelog is available if you’re interested in all of the details.

Here are the summarized improvements:

  • Fixed multiple Solaris bugs
  • Fixed some reporting bugs
  • Adjusted some recommendations

Although no new features were added, the additional Solaris support has been well received. Of course, if you find bugs, have questions, or want to join in the project, head on over to the MySQLTuner Talk Google Group.

Printed from: http://blog.mysqltuner.com/2009/09/mysqltuner-v1-1-0-released/ .
© Major Hayden 2010.

12 Comments   »

  1. toca says:

    First thanks for providing this script, it have been extremely useful for me and very convenient too :-)

    I didn’t find the download on your site though.
    the download page states wget mysqltuner.pl but no url.
    not a problem, I downloaded it from github, just wondered.

  2. Hey toca,

    You can actually just hop into a terminal and type exactly this:

    wget mysqltuner.pl

    I bought the ‘mysqltuner.pl’ domain name (.pl is a Polish TLD) and it redirects directly to the script. Let me know if you’re still having problems!

    • John Thomas says:

      Ha! I could not figure out your download page at first. I thought you left off the domain. Perhaps you could add that the script can be viewed in a browser at http://mysqltuner.pl

      Very cool script!! Thank you for it.

    • carl^ says:

      I had to read this comment to find that out, but very nice idea! (now considering doing something similar using a .sh domain)#

      Great script too!

      Thanks

  3. Nils Breunese says:

    A little bug: 1.1.0 reports as 1.0.1 (my $tunerversion = “1.0.1″;).

  4. Rowan says:

    Just a note on using it with mysql 5.1.3+ the table_cache is now table_open_cache

  5. Håkan Askengren says:

    Hi
    Great script.
    Is there a way to get output better formatted when writing to file? example;
    perl mysqltuner.pl > mysqltuner_20091015.log
    ?

  6. Dukla says:

    ——– General Statistics ————————————————–
    [--] Skipped version check for MySQLTuner script
    [OK] Currently running supported MySQL version 5.1.37-1ubuntu5
    [OK] Operating on 64-bit architecture

    ——– Storage Engine Statistics ——————————————-
    [--] Status: -Archive -BDB -Federated +InnoDB -ISAM -NDBCluster
    [--] Data in MyISAM tables: 1M (Tables: 12)
    [--] Data in InnoDB tables: 1G (Tables: 57)
    [!!] Total fragmented tables: 57

    ——– Security Recommendations ——————————————-
    [OK] All database users have passwords assigned

    ——– Performance Metrics ————————————————-
    [--] Up for: 57m 41s (2K q [0.641 qps], 93 conn, TX: 207K, RX: 950M)
    [--] Reads / Writes: 10% / 90%
    [--] Total buffers: 58.0M global + 2.7M per thread (151 max threads)
    [OK] Maximum possible memory usage: 463.8M (5% of installed RAM)
    [OK] Slow queries: 0% (0/2K)
    [OK] Highest usage of available connections: 1% (2/151)
    [OK] Key buffer size / total MyISAM indexes: 16.0M/430.0K
    [OK] Key buffer hit rate: 98.4% (29K cached / 472 reads)
    [!!] Query cache efficiency: 2.5% (3 cached / 121 selects)
    [OK] Query cache prunes per day: 0
    [OK] Sorts requiring temporary tables: 0% (0 temp sorts / 2 sorts)
    [OK] Temporary tables created on disk: 21% (57 on disk / 269 total)
    [OK] Thread cache hit rate: 97% (2 created / 93 connections)
    [!!] Table cache hit rate: 4% (57 open / 1K opened)
    [OK] Open file limit used: 0% (0/1K)
    [OK] Table locks acquired immediately: 100% (684 immediate / 684 locks)
    [!!] Connections aborted: 8%
    [!!] InnoDB data size / buffer pool: 1.2G/8.0M

    ——– Recommendations —————————————————–
    General recommendations:
    Run OPTIMIZE TABLE to defragment tables for better performance
    MySQL started within last 24 hours – recommendations may be inaccurate
    Enable the slow query log to troubleshoot bad queries
    Increase table_cache gradually to avoid file descriptor limits
    Your applications are not closing MySQL connections properly
    Variables to adjust:
    query_cache_limit (> 1M, or use smaller result sets)
    table_cache (> 64)
    innodb_buffer_pool_size (>= 1G)

RSS feed for comments on this post , TrackBack URI

Leave a Comment


Fork me on GitHub