For anyone, who has questions about MySQL query cache tuning, try this tuning assistant:
-
Recent Posts
Recent Comments
Archives
Categories
Tags
backup benchmarks conference crash dba dtrace funny gcc gdb google innodb io joke knol linux memcached memory mmap mydumper myisam mysql mysqlconf mysqluc performance presentation profiling raid rant recovery replication san francisco security session solaris sun talk threading timstarling tools trip tutorial web4 xfs xss zfs
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:
Why?
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.
http://twitter.com/datacharmer/status/2538537477
But I liked your optimization operator more.
Cheers
Giuseppe
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
domas you rock!
rock on!
agree…
I agree
http://bugs.mysql.com/bug.php?id=45544