query cache tuning

13 thoughts on “query cache tuning”

1. Nice guide, concise and to the point…

2. Hum, okay. But I’ll ask one question that everyone finding this post via Google will ask anyways:

   Why?

   1. Because, short term hacks shouldn’t win over proper data structuring, indexing and queries :)

3. Why? Obviously because you want to tune your query cache.

   .. ahem.. sorry…

   The MySQL query cache can be a very useful tool, but if you have a high volume of queries and you don’t tune it properly it can become a bottleneck. By tuning the QC you eliminate that bottleneck and (hopefully) improve performance.

   1. How does one tune away the mutex contention? It does not scale on multi-core servers.

   2. So 0 is the best tuning you can have. Sure.

4. I like it, and I advertised it.

   RT @mysql_community: Extremely funny, possibly helpful, and certainly assertive advice on query cache tuning. http://bit.ly/jwulW

   — Giuseppe Maxia (@datacharmer) July 8, 2009

   But I liked your optimization operator more.

   Cheers

   Giuseppe

5. I cant get to the URL or the guide you have told can you repost the correct URL. It can be of great help !!

   Thanks

6. domas you rock!
   rock on!

7. agree…

8. I agree

   http://bugs.mysql.com/bug.php?id=45544

9. This is a bug report for your online query cache tuner.

   It doesn’t also say to set query_cache_type = 0 if your MySQL version is 5.5 or higher, to eliminate taking the qc mutex.

   Bet you never thought you’d get a bug report on that. :)

   1. I ignore 5.5! ;-)

Comments are closed.