Comments on: Making query cache contention more obvious http://www.xaprb.com/blog/2010/09/15/making-query-cache-contention-more-obvious/ Stay curious! Fri, 10 May 2013 18:25:19 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Shlomi Noach http://www.xaprb.com/blog/2010/09/15/making-query-cache-contention-more-obvious/#comment-18665 Shlomi Noach Fri, 17 Sep 2010 09:08:23 +0000 http://www.xaprb.com/blog/?p=2016#comment-18665 Good!

]]> By: Mark Leith http://www.xaprb.com/blog/2010/09/15/making-query-cache-contention-more-obvious/#comment-18664 Mark Leith Fri, 17 Sep 2010 06:21:13 +0000 http://www.xaprb.com/blog/?p=2016#comment-18664 PERFORMANCE_SCHEMA will show the number of query cache mutex waits, the amount of time waiting for the mutex, and whether any sessions are currently waiting on it.. :)

]]> By: Shlomi Noach http://www.xaprb.com/blog/2010/09/15/making-query-cache-contention-more-obvious/#comment-18662 Shlomi Noach Thu, 16 Sep 2010 05:21:50 +0000 http://www.xaprb.com/blog/?p=2016#comment-18662 Baron, this is good news. It has always been hard to prove that the query cache makes for trouble.

However, even better would be a status variable like “Qcache_lock_waits”, similar to table locks or innodb locks. This ways it would be easier to see+measure the contention on the qcache. Catching it on the processlist is more difficult if you do sample monitoring.

]]> By: Antony Curtis http://www.xaprb.com/blog/2010/09/15/making-query-cache-contention-more-obvious/#comment-18661 Antony Curtis Thu, 16 Sep 2010 05:15:40 +0000 http://www.xaprb.com/blog/?p=2016#comment-18661 I just prefer to configure and build without query cache.

]]>