<?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: Filesystem scaling in high traffic web applications</title>
	<atom:link href="http://greg.nokes.name/2008/12/25/filesystem-scaling-in-high-traffic-web-applications/feed/" rel="self" type="application/rss+xml" />
	<link>http://greg.nokes.name/2008/12/25/filesystem-scaling-in-high-traffic-web-applications/</link>
	<description>A wayward journey into the depths of sanity</description>
	<lastBuildDate>Sun, 29 Aug 2010 22:08:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: DaRoost &#187; Blog Archive &#187; Scaling Wide</title>
		<link>http://greg.nokes.name/2008/12/25/filesystem-scaling-in-high-traffic-web-applications/comment-page-1/#comment-1164</link>
		<dc:creator>DaRoost &#187; Blog Archive &#187; Scaling Wide</dc:creator>
		<pubDate>Fri, 03 Jul 2009 22:20:50 +0000</pubDate>
		<guid isPermaLink="false">http://30/2008/12/27/filesystem-scaling-in-high-traffic-web-applications#comment-1164</guid>
		<description>[...] If your application is filesystem IOPS heavy, filesystem sharding might be the route that you want to look at. Basically you add more hardware disk arrays, and split the reads and writes between them. You need to inject some logic into the save and open functions in your application so that it knows which filesystem each file is to be saved to and opened from. Usually you create a hash of the filename, and key off the first couple of characters in the hash. You can read more on this technique here. [...]</description>
		<content:encoded><![CDATA[<p>[...] If your application is filesystem IOPS heavy, filesystem sharding might be the route that you want to look at. Basically you add more hardware disk arrays, and split the reads and writes between them. You need to inject some logic into the save and open functions in your application so that it knows which filesystem each file is to be saved to and opened from. Usually you create a hash of the filename, and key off the first couple of characters in the hash. You can read more on this technique here. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
