nothing to worry that bad about, nevertheless, in my mysql log the query
SELECT option_value, option_name FROM piwik_option WHERE autoload = 1;
appeared. This query does not use an index on the column autoload. As it contains not that much stuff the performance issue is not that dramatic but it gives spaces for optimisation at this point.
Or have there been any special reasons which I did not consider, yet?
Is there a MySQL message?
Nevermind. I found the setting: http://dev.mysql.com/doc/refman/5.0/en/server-options.html#option_mysqld_log-queries-not-using-indexes
matt: add an index for autoload, option name, or both?
Well in this specific case i just checked with this one parameter autoload for selection and setting an additional indey for this column.
Maybe its worth a check to do an explain select on this query with both types of indexes and an in case the index of both fields does fine, too just measure the qeuery speed.
the primary key is option name already. I think it makes sense to add an index on autoload, to help the query autoloading the core _option values.
Given how _option is used in product, storing settings for websites and users, this suggestion makes sense.
(In ) Page titles report improvements fixes #1898
Improvements to integration tests