For anyone, who has questions about MySQL query cache tuning, try this tuning assistant:
Nice guide, concise and to the point…
Hum, okay. But I’ll ask one question that everyone finding this post via Google will ask anyways:
Because, short term hacks shouldn’t win over proper data structuring, indexing and queries :)
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.
How does one tune away the mutex contention? It does not scale on multi-core servers.
So 0 is the best tuning you can have. Sure.
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 08, 2009
But I liked your optimization operator more.
I cant get to the URL or the guide you have told can you repost the correct URL. It can be of great help !!
domas you rock!
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. :)
I ignore 5.5! ;-)
Comments are closed.
Get every new post delivered to your Inbox.
Join 622 other followers