Optimising and caching your MySQL enquiries
Archive - Originally posted on "The Horse's Mouth" - 2010-02-22 09:22:10 - Graham EllisIf you want to get a list of all the different values in a column, but don't care how many times each occurs, you can apply the DISTINCT keyword on your SELECT. See [here]. The DISTINCTROW is a synonym of DISTINCT, and the default is ALL which you may also state.
MySQL Caches queries - so that if it receives an identical query for a second time, it doesn't have to do all the hard work again. MySQL is aware of changes that may be made to the tables, so that it can identify when the results would be changed and so it needs to re'calculate', so most of the time you can simply say "Thank you" for the facility and write code that repeats the same query many times over, secure in the knowledge that MySQL will spot your inefficiencies (it does this across sessions too - see [here]). There are, however, times that you don't want caching to be running - the most common example is if you're benchmarking your application and you want to see if a change that you've made has made things faster or slower; in such a situation, cached results will cause major variations in the times you get which are not related to the software changes that you're making. You can apply the SQL_NO_CACHE keyword to your select statement to ensure that the results you generate are not saved in the cache ... so that subsequent requests will not refer back to this results set. [[You can set SQL_CACHE if you explicitly want caching on; it's the default]]
| Aside - although MySQL will help you by using the cache when it's sure that it can, you should not rely on it as a crutch for your own sloppy, repeated coding. It will err on the side of caution and recalculate if there's any possible doubt, and when you think of it, that's a far better solution than risking wrong results! |
Other keywords that you can apply directly after the SELECT are:
HIGH_PRIORITY - Do the SELECT in preference to any outstanding updates
STRAIGHT_JOIN - For optimizing joins (to help the built in optimiser)
SQL_SMALL_RESULT, SQL_BIG_RESULT, SQL_BUFFER_RESULT - To help MySQL optimise its performance based on the anticipated size of the result set
SQL_CALC_FOUND_ROWS - If you're doing a query and only asking for some of the results back through LIMIT, this keyword will tell MySQL go go ahead and find ALL the results not just the few you want, in so far as it will be able to tell you how big the result set would have been without the LIMIT.
The extra keywords are MySQL extensions to the SQL standard, and if you use them you'll restrict the portability of your code (that may not be a problem to you ... but it's worth bearing in mind if you may use a different database engine in the future!)