<?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 Query Cache</title>
	<atom:link href="http://aptoma.com/select.star/2009/10/22/mysql-query-cache/feed/" rel="self" type="application/rss+xml" />
	<link>http://aptoma.com/select.star/2009/10/22/mysql-query-cache/</link>
	<description>web-development, and other issues we really, really care about</description>
	<lastBuildDate>Thu, 22 Apr 2010 20:30:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Caching Strategies (AMS week #43) &#187; select *</title>
		<link>http://aptoma.com/select.star/2009/10/22/mysql-query-cache/comment-page-1/#comment-7808</link>
		<dc:creator>Caching Strategies (AMS week #43) &#187; select *</dc:creator>
		<pubDate>Mon, 26 Oct 2009 08:39:35 +0000</pubDate>
		<guid isPermaLink="false">http://aptoma.com/select.star/?p=809#comment-7808</guid>
		<description>[...] If you need to squeeze out every bit of performance available from your application, you should switch to the DEMAND-setting, and review all your SQL-statements and judiciously use the SQL CACHE-trigger. If you have the time and skill to do this, you will benefit from it. You would want to use it on tables with a high percentage of read over write requests. Using SQL-CACHE on tables with a lot of writes will only hurt your overall performance. (Lars has more to say on the topic of Query Cache) [...]</description>
		<content:encoded><![CDATA[<p>[...] If you need to squeeze out every bit of performance available from your application, you should switch to the DEMAND-setting, and review all your SQL-statements and judiciously use the SQL CACHE-trigger. If you have the time and skill to do this, you will benefit from it. You would want to use it on tables with a high percentage of read over write requests. Using SQL-CACHE on tables with a lot of writes will only hurt your overall performance. (Lars has more to say on the topic of Query Cache) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
