<?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"
	>
<channel>
	<title>Comments on: Cascade File System and Build Performance</title>
	<atom:link href="http://www.conifersystems.com/2008/09/16/cfs-build-performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.conifersystems.com/2008/09/16/cfs-build-performance/</link>
	<description></description>
	<pubDate>Sun, 05 Feb 2012 09:56:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Matt</title>
		<link>http://www.conifersystems.com/2008/09/16/cfs-build-performance/#comment-5</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Mon, 22 Sep 2008 07:44:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.conifersystems.com/?p=42#comment-5</guid>
		<description>A valid concern.  Of course, we have to compare apples to apples: if you count the time to service cache misses with CFS, then you also have to count the time to check out or update your tree without CFS.  That's a more complex issue; I'm just trying to clarify that CFS (by itself) does not impose a significant performance hit.</description>
		<content:encoded><![CDATA[<p>A valid concern.  Of course, we have to compare apples to apples: if you count the time to service cache misses with CFS, then you also have to count the time to check out or update your tree without CFS.  That&#8217;s a more complex issue; I&#8217;m just trying to clarify that CFS (by itself) does not impose a significant performance hit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Carter</title>
		<link>http://www.conifersystems.com/2008/09/16/cfs-build-performance/#comment-4</link>
		<dc:creator>Nick Carter</dc:creator>
		<pubDate>Sat, 20 Sep 2008 17:49:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.conifersystems.com/?p=42#comment-4</guid>
		<description>I understand the desire to reduce measurement variability by doing only warm runs, but is a fully populated cache the situation that most users will find themselves in?</description>
		<content:encoded><![CDATA[<p>I understand the desire to reduce measurement variability by doing only warm runs, but is a fully populated cache the situation that most users will find themselves in?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

