MySQL Optimization Hints
Every programmer loves to optimize, even when we know we shouldn't. To satisfy your cravings MySQL has several keywords that can be placed in your SQL statement to give the database server an explicit optimization instruction.
I should point out that using the hints incorrectly will most likely cause your queries to perform worse, so be sure that it actually makes sense to use them before you go nuts. This means use
EXPLAIN and read the documentation on each hint before using.
It's also a good idea to enclose the hints within a SQL comment, for example
SELECT /*! SQL_NO_CACHE */ columns FROM table. This can help to make your application a bit more portable.
Let's take a look at some MySQL Optimization Hints:
SQL_NO_CACHE hint turns off MySQL's builtin query caching mechanism for a particular query. You can help MySQL make the query cache more efficient by using this hint on queries that are highly dynamic (such as a keyword search, or a report that only runs nightly). Make sure query caching is turned on otherwise there is no need for this command.
Checkout my article on the MySQL Query Cache for more info.
If you have setup MySQL Query Caching to explicit mode (set
query_cache_type = 2) then you can use the
SQL_CACHE hint to tell MySQL which queries to cache.
My article on the MySQL query cache also covers this hint.
HIGH_PRIORITY hint can be used on
INSERT statements to let MySQL know that this is a high priority query. This hint will basically allow the query to skip in line.
LOW_PRIORITY hint can be used on
If you use the
LOW_PRIORITY keyword, execution of the query is delayed until no other clients are reading from the table. This means that you may wait a LONG time, or forever on servers with a heavy read volume.
INSERT LOW_PRIORITY statement will not return until the statement has been executed, which could possibly be forever. Instead you can use an
INSERT DELAYED statement. It will return immediately, but it will still wait until other clients have closed the table before executing the statement.
I have written an article on MySQL Insert Delayed as well.
INSERT DELAYED only works on MyISAM, MEMORY, and ARCHIVE tables.
This hint will tell MySQL to join the tables in the order that they are specified in the
EXPLAIN to make sure that MySQL has not already figured out the optimal join order. And if you specify an ill order you can make MySQL do a lot more work than it needs to.
This hint tells MySQL to put the result of the query into a temporary table. This will free up a table lock while the result set is being sent to the client. So you would only want to use this on large result sets.
SQL_BIG_RESULT hint can be used with
SELECT statements. It as you might guess, tells MySQL that the result set will be big. According to the MySQL documentation, if invoked
MySQL directly uses disk-based temporary tables if needed, and prefers sorting to using a temporary table with a key on the GROUP BY elements.
AS you might guess this is pretty much the opposite of
SQL_BIG_RESULT. When enabled MySQL uses fast temporary tables to store the resulting table instead of using sorting. Since this is typically the default route of the optimizer, this hint is often not needed.
Finally it is always good to stay up to date with MySQL Patches. Here is a good resource for staying current with MySQL Security Patches.
Like this? Follow me ↯Tweet Follow @pfreitag
You might also like:
- Google Video: MySQL Performance Tuning Best Practices - May 11, 2006
- Premature optimization is the root of all evil - December 8, 2005
- Insert Delayed with MySQL - August 2, 2005
- The MySQL Query Cache - June 21, 2005
- High Performance MySQL - April 28, 2005
- OutOfMemoryError - GC overhead limit exceeded - March 25, 2010
- 8 Ways to Save Bandwidth on your RSS Feed - July 12, 2007
- Java Performance Tuning Guide - December 7, 2005