<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: MySQL Tuning: Disable Query Cache on Frequently Updated Databases</title>
	<atom:link href="http://www.dangrossman.info/2007/04/26/mysql-tuning-disable-query-cache-on-frequently-updated-databases/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dangrossman.info/2007/04/26/mysql-tuning-disable-query-cache-on-frequently-updated-databases/</link>
	<description></description>
	<lastBuildDate>Mon, 08 Mar 2010 15:03:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tuning and Optimizing Performace of MySQL &#124; lonerunners.net</title>
		<link>http://www.dangrossman.info/2007/04/26/mysql-tuning-disable-query-cache-on-frequently-updated-databases/comment-page-1/#comment-62642</link>
		<dc:creator>Tuning and Optimizing Performace of MySQL &#124; lonerunners.net</dc:creator>
		<pubDate>Sun, 02 Nov 2008 00:35:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.dangrossman.info/2007/04/26/mysql-tuning-disable-query-cache-on-high-volume-databases/#comment-62642</guid>
		<description>[...] MySQL Tuning: Disable Query Cache on Frequently Updated Databases [...]</description>
		<content:encoded><![CDATA[<p>[...] MySQL Tuning: Disable Query Cache on Frequently Updated Databases [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://www.dangrossman.info/2007/04/26/mysql-tuning-disable-query-cache-on-frequently-updated-databases/comment-page-1/#comment-20065</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Sun, 29 Apr 2007 01:26:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.dangrossman.info/2007/04/26/mysql-tuning-disable-query-cache-on-high-volume-databases/#comment-20065</guid>
		<description>The setting for on demand is:
query_cache_type = 2

Then you&#039;d add the SQL_CACHE hint to the SELECT queries to have them cached:
SELECT SQL_CACHE [columns] FROM [table] ...</description>
		<content:encoded><![CDATA[<p>The setting for on demand is:<br />
query_cache_type = 2</p>
<p>Then you&#8217;d add the SQL_CACHE hint to the SELECT queries to have them cached:<br />
SELECT SQL_CACHE [columns] FROM [table] &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chemist</title>
		<link>http://www.dangrossman.info/2007/04/26/mysql-tuning-disable-query-cache-on-frequently-updated-databases/comment-page-1/#comment-20044</link>
		<dc:creator>Chemist</dc:creator>
		<pubDate>Sun, 29 Apr 2007 00:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.dangrossman.info/2007/04/26/mysql-tuning-disable-query-cache-on-high-volume-databases/#comment-20044</guid>
		<description>&lt;blockquote cite=&quot;You may be able to do that if you change the query cache type to â€œon demandâ€ and explicitly tell it which SELECT queries you want cached&quot;&gt;

So in my.cnf I would add:

query_cache_type on demand

But how do you specify the queries to cache?</description>
		<content:encoded><![CDATA[<blockquote cite="You may be able to do that if you change the query cache type to â€œon demandâ€ and explicitly tell it which SELECT queries you want cached">
<p>So in my.cnf I would add:</p>
<p>query_cache_type on demand</p>
<p>But how do you specify the queries to cache?</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://www.dangrossman.info/2007/04/26/mysql-tuning-disable-query-cache-on-frequently-updated-databases/comment-page-1/#comment-18982</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Thu, 26 Apr 2007 23:03:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.dangrossman.info/2007/04/26/mysql-tuning-disable-query-cache-on-high-volume-databases/#comment-18982</guid>
		<description>You may be able to do that if you change the query cache type to &quot;on demand&quot; and explicitly tell it which SELECT queries you want cached. Otherwise, my fear is SELECT queries against those other tables might knock longer-lasting SELECTs out of the smaller cache before being quickly removed themselves. In either scenario here, there&#039;s still overhead attached to the UPDATE and INSERT queries checking if they invalidate something in the cache. Only turning off the cache removes that overhead entirely.</description>
		<content:encoded><![CDATA[<p>You may be able to do that if you change the query cache type to &#8220;on demand&#8221; and explicitly tell it which SELECT queries you want cached. Otherwise, my fear is SELECT queries against those other tables might knock longer-lasting SELECTs out of the smaller cache before being quickly removed themselves. In either scenario here, there&#8217;s still overhead attached to the UPDATE and INSERT queries checking if they invalidate something in the cache. Only turning off the cache removes that overhead entirely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seun Osewa</title>
		<link>http://www.dangrossman.info/2007/04/26/mysql-tuning-disable-query-cache-on-frequently-updated-databases/comment-page-1/#comment-18979</link>
		<dc:creator>Seun Osewa</dc:creator>
		<pubDate>Thu, 26 Apr 2007 22:55:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.dangrossman.info/2007/04/26/mysql-tuning-disable-query-cache-on-high-volume-databases/#comment-18979</guid>
		<description>How about just reducing the size of the query cache so the small queries on less frequently updated tables will remain in the cache?</description>
		<content:encoded><![CDATA[<p>How about just reducing the size of the query cache so the small queries on less frequently updated tables will remain in the cache?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
