mysqltuner

Including mysql tuner into phpMyAdmin

Asked by tyronm

Hi, I was wondering is still project still being developed/maintained? And why hasn't it been merged with the original mysql tuner? (mysqltuner.com)

As part of my project proposal for Google Summer of Code I am interested in including the tuning rules from this project. Though I will need to rewrite them into PHP and would like to provide more information to the user by defining different warn levels. (e.g. uptime only some hours => very inaccurate, uptime less than a day => somewhat inaccurate) and giving the user an explanation to each recommendation.
Since in my case, this is all displayed within the browser, I have much more possibilities in displaying this information.

So with this question I also am wondering if there is any strong objections to my plan in including mysqltuner into phpMyAdmin. I would, of course, mention the original authors and project sites.

And if this project is still being maintained, it might be a good idea if we agree on a common rule file format so they can be used interchangeably between our projects. That would be pretty cool, don't you think? :-)

Question information

Language:
English Edit question
Status:
Answered
For:
mysqltuner Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Sheeri K. Cabral (awfief) said : 		#1

Tyronm -

The project hasn't been merged into mysqltuner 1.0 because 2.0 doesn't have all the functionality of 1.0 yet. You may include the tuning rules, however, they're not rules. The entire spirit of the mysqltuner 2.0 project was that you need to know what you're doing to use mysqltuner and that the "rules" in mysqltuner 2.0 were very changeable.

Putting the tuning "rules" as you call them, into phpMyAdmin, is completely against the spirit of mysqltuner 2.0. Which would be fine, because everyone has their own ideas, except that what the rules are change depending on how MySQL is used, and also change based on improvements to MySQL and other technologies. (for instance, the query_cache used to be a good idea, but with the advent of memcached, the query_cache is generally to be avoided, except in specific instances where it really is the best way to handle caching....but that's only about 1% of the time these days).

So, you can go ahead and put that all into phpMyAdmin -- I don't *object* but I'd heavily warn against it, because really the problem with mysqltuner 1.0 is that the thresholds are hard-coded and misleading.....any set of "rules" would be.

You might want to check out the video at http://www.youtube.com/watch?v=694UjjtRr5o which explains everything....it's worth your while.

If, after watching the video and understanding the caveats, you still want to put mysqltuner into phpMyAdmin, go for it.

As for a common rule file format, what is wrong with using the format that already exists with mysqltuner?

Revision history for this message
tyronm (tyronx) said : 		#2

Yes, I very much understand the idea behind it. Which is why I tried to keep the mysqltuner 2.0 spirit for building the concept of a integrated tuner.

- I've tried to keep the rules / config file as interchangeable and flexible as possible. What I did to the config file is to build a slightly more extended syntax that allows more textual explanation to each recommendation. Here is the current version of it: http://www.tyron.at/tmp/advisory_rules.txt (which I will have to adjust for i10n though)
It is somewhat adjusted to the needs of phpMyAdmin, e.g. there is no output from each rule unless it's condition evaluated correctly, because within phpMyAdmin one can look up status values on another tab.

- As you mention in your presentation video my proposed feature is intended mostly just for a quick sanity check. Some of the recommendations might be wrong indeed - for that reason I've kept the config file interchangeable and display how the value is calculated, so that every slightly more experienced dba can verify it's results. Here's a screenshot how it currently looks like: http://www.tyron.at/tmp/pmatuner.jpg

As for the rule file format, I just realized since phpmyadmin and mysqltuner2.0 works in a very different enviroment, it's probably not to useful to same have the format after all.

Thank you very much for your feedback. I'll see that I also add some info about memcached :)

Revision history for this message
Sheeri K. Cabral (awfief) said : 		#3

Tyronm - sounds like you have a good grasp of what's going on and understand the nuances of the issue.

I look forward to seeing what you do!

Revision history for this message
tyronm (tyronx) said : 		#4

You can actually try it out already if you like to :)
Just browse to http://demo.phpmyadmin.net/gsoc-tyron/, login as root with no pass, then navigate to Status => Advisor

Can you help with this problem?

Provide an answer of your own, or ask tyronm for more information if necessary.

To post a message you must log in.