<?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: The Problem With I/O</title>
	<atom:link href="http://lonesysadmin.net/2006/07/25/the-problem-with-io/feed" rel="self" type="application/rss+xml" />
	<link>http://lonesysadmin.net/2006/07/25/the-problem-with-io/</link>
	<description>im in ur data centrz patchin ur serverz</description>
	<pubDate>Fri, 21 Nov 2008 22:53:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Chris Adams</title>
		<link>http://lonesysadmin.net/2006/07/25/the-problem-with-io/#comment-4417</link>
		<dc:creator>Chris Adams</dc:creator>
		<pubDate>Tue, 25 Jul 2006 18:40:26 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2006/07/24/the-problem-with-io/#comment-4417</guid>
		<description>I'm really looking forward to ZFS spreading for precisely this reason - I can't wait to get out of the micro-optimization business and ZFS has automatic hotspot balancing across the entire pool. You can basically wait for there to be a problem (pool-wide - completely avoiding the problems with small volumes being trivially spindle-limited) and add an extra/faster drive (which can be anything accessible by the system - you could buy some time to deal with a SCSI hotspot by tossing SAN storage at it or even a USB/firewire drive if you were really desperate). 

One of the developers likes to tell an anecdote about this flushed out some differences in the drive settings on a RAID enclosure which one of the beta testers used - the tester was wondering why one drive's activity LED flickered less often and learned that ZFS had noticed that it was slower than the others and wasn't using it for hot data.</description>
		<content:encoded><![CDATA[<p>I&#8217;m really looking forward to ZFS spreading for precisely this reason - I can&#8217;t wait to get out of the micro-optimization business and ZFS has automatic hotspot balancing across the entire pool. You can basically wait for there to be a problem (pool-wide - completely avoiding the problems with small volumes being trivially spindle-limited) and add an extra/faster drive (which can be anything accessible by the system - you could buy some time to deal with a SCSI hotspot by tossing SAN storage at it or even a USB/firewire drive if you were really desperate). </p>
<p>One of the developers likes to tell an anecdote about this flushed out some differences in the drive settings on a RAID enclosure which one of the beta testers used - the tester was wondering why one drive&#8217;s activity LED flickered less often and learned that ZFS had noticed that it was slower than the others and wasn&#8217;t using it for hot data.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
