[mattlegrand]

Thats perfect. Thanks again 🙂

[mattlegrand]

Hi Ernest,

Unfortunately, I don’t have THAT perfect tool to track queries we all wish to have. However, if that can help, I use two that you don’t seem to.

1) I enable slow query log that is built-in in MySQL. I set it to 1 seconds, so every query that is not lightning fast is recorded with details about disk usage.

2) I use a console app « mytop » (the little brother of the top command for MySQL) which shows what query is being run with the server load. Pretty simple, but if you check it for a while you get an idea of what is being queried too much.

I’ve set the trigger at 3 character. IMO, it gonna really help.

Also, I’ve figured why the SHOW TABLE sticks out so much, it’s because on my server it’s slow (over 2 seconds). I run a WordPress MultiSite where Quebec citizens can create free/paid blogs and over the years there’s just way way too many tables in that database.

Has it been fixed in the new version or do you plan to do so in the future? I might have to hack it otherwise and I don’t really want to 🙂

Thanks a lot,

Cheers!

[mattlegrand]

Hi Ernest,

I really appreciate the effort you put in your response. God knows, it’s rare to have good support.

I think I have found what may cause a part of the overhead. I enabled statistics and in a few hours I gathered a lot of “No keyword” searches. I wonder what may cause that? Is it because it’s the first thing on my page and it might autofocus on some browser?

Also, concerning the “SHOW TABLE” thing. The problem is that, as a query it is not cachable and mysql does write a temp table to disk to produce the result. It would be much more efficient to set a flag with update_option once you found it and then use get_option to check if it has been created since those query will get cached either by a WordPress Caching Plugin, Redis/Varnish or MySQL.

Anyway, I’m still happy.

Have a nice day.

[Author]

Posts