Week 11 report

This week I have been coding hard on the Advisor system that I planned for a long time. It uses the mysqltuner 2.0 config as a base, though I have added much more information about each rule/recommendation.

Here is an example rule in mysqltuner2.0

Query cache efficiency (%)|||<20|||Qcache_hits/(Com_select+Qcache_hits)*100|||query cache not efficient, consider increasing query_cache_limit.

This is how it looks in the pma version:

rule 'Query cache efficiency (%)' [Com_select + Qcache_hits > 0 && !fired('Query cache disabled')]

Qcache_hits / (Com_select + Qcache_hits) * 100

value < 20

Query cache not running efficiently, it has a low hit rate.

Consider increasing {query_cache_limit}.

The current query cache hit rate of %s% is below 20% | round(value,1)

As you can see, there is now 3 text lines. They are displayed title with 'issue','recommendation' and 'justification'. This way the user can make a more wise decision on how to improve the performance (or ignore the recommendation altogether)

This rule syntax is being parsed by a simple rules engine I have coded this week.

What I made this week:

- Advisor system:

  - Built rules file and rules parser

  - User interface that displays the recommendations

- New status variables "filter" that allows one to display the unformatted values (so one can copy and calculate own perfomance measures)

- Fixed a security issues with last weeks changes and other small improvements

What I will do next week:

- I will need to find a good way of adding i10n to the rules file

- Improve code style, write documentation etc.

- With leftover time, build some of the features from last weeks idea list (week 10 blog report)