Comments on: query cache tuning

By: Mohammad Lahlouh

Mohammad Lahlouh — Thu, 09 Jul 2009 13:52:28 +0000

I agree

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

By: Julian

Julian — Thu, 09 Jul 2009 08:31:41 +0000

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

By: Willko

Willko — Thu, 09 Jul 2009 08:13:44 +0000

agree…

By: Domas Mituzas

Domas Mituzas — Thu, 09 Jul 2009 06:34:25 +0000

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

By: Mark Callaghan

Mark Callaghan — Thu, 09 Jul 2009 04:41:50 +0000

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

By: erkules

erkules — Wed, 08 Jul 2009 23:37:25 +0000

domas you rock!
rock on!

By: Sandy

Sandy — Wed, 08 Jul 2009 22:14:04 +0000

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

By: Giuseppe Maxia

Giuseppe Maxia — Wed, 08 Jul 2009 21:58:16 +0000

I like it, and I advertised it.
http://twitter.com/datacharmer/status/2538537477
But I liked your optimization operator more.

Cheers

Giuseppe

By: Justin Swanhart

Justin Swanhart — Wed, 08 Jul 2009 20:27:37 +0000

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.

By: Julian

Julian — Wed, 08 Jul 2009 20:12:21 +0000

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

Why?

By: figvam

figvam — Wed, 08 Jul 2009 18:47:45 +0000

Nice guide, concise and to the point…