Have a look at DBI::Profile.

McA

Hi,

some additions. The company Percona* (www.percona.com) does provide some MySQL related tools which can also be used against a non-percona MySQL server. These tools are bundled under the name "Percona Toolkit for MySQL".

How does this fit here? This toolkit is written in perl, it's open source and provided with a GNU v2 license.

One script of that is pt-query-digest which aggregates informations from the slow query log. In newer MySQL versions you can even log every statement, so that you get an overview over all statements over time. As far as I know the script or a companion script gives advice how to improve the statements found.

Probably worth a try. (@Voronich: Something for you?)

Best regards
McA

* That is no advertisment from my side

The EXPLAIN verb can be used to show you the “execution plan” of any SQL statement ... this being the actual sequence of low-level operations that the query engine will carry out in order to do what the query says to do.   It is often the case that “there’s more than one way to do it,” but that one of them will be noticeably better than the others.

You can obtain slight speedups by “preparing a statement-handle” once, then using it to execute the same query multiple times, changing the set of parameters that you give it each time.

How many queries-per-second are you running, and what sort of queries are they?   Are the tables InnoDB?   Transactions?