I've been thinking about how to improve the tuning calculations to know when to stop. For several of the variables the script will continue to tell you to increase ad infinitum. Unfortunately I think we get to a point where the script can no longer help, you actually need to do some A/B testing to see which is better for your specific situation. Perhaps we should include some sort of disclaimer along these lines.

Comments

mikeytown2’s picture

Title: DB Tuning disclaimer » DB Tuning disclaimer and/or make tuner configuration more specific to Drupal's usage of MySQL.

Followup from this I take it ;)
http://groups.drupal.org/node/97129

We could create out own version of tuner-default.cnf; or translate that from perl to php one last time and make it more drupal specific. I think this would be a good idea; make the tuner more Drupal specific. I would be opt for 100% php; just means I need to keep an eye on https://code.launchpad.net/~mysqltuner-dev/mysqltuner/devel for any commits (something I already do) and adjust accordingly.

mikeytown2’s picture