<?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: Self tuning storage?</title>
	<atom:link href="http://blog.nigelpoulton.com/self-tuning-storage/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nigelpoulton.com/self-tuning-storage/#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
	<description>with nigel poulton</description>
	<lastBuildDate>Tue, 20 Dec 2011 19:37:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris M Evans</title>
		<link>http://blog.nigelpoulton.com/self-tuning-storage/comment-page-1/#comment-181</link>
		<dc:creator>Chris M Evans</dc:creator>
		<pubDate>Mon, 14 May 2007 18:50:27 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=85#comment-181</guid>
		<description>Right on the money, Nigel.&#160; In fact I&#039;d go as far as to suggest that EMC, HDS and IBM (although I have little knowledge of their products) are amending their arrays to fix inherent problems with their design - like having to have disks on FC-AL loops which then require moving data between physical disks to manage performance.&#160; Rather than developing &quot;self-optimising&quot; arrays, I think they&#039;re all putting sticking plasters over the problem.</description>
		<content:encoded><![CDATA[<p>Right on the money, Nigel.&nbsp; In fact I&#8217;d go as far as to suggest that EMC, HDS and IBM (although I have little knowledge of their products) are amending their arrays to fix inherent problems with their design &#8211; like having to have disks on FC-AL loops which then require moving data between physical disks to manage performance.&nbsp; Rather than developing &quot;self-optimising&quot; arrays, I think they&#8217;re all putting sticking plasters over the problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nigel</title>
		<link>http://blog.nigelpoulton.com/self-tuning-storage/comment-page-1/#comment-180</link>
		<dc:creator>nigel</dc:creator>
		<pubDate>Mon, 14 May 2007 11:47:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=85#comment-180</guid>
		<description>Hi Ewan,
I hear what your saying.&#160; sounds similar to the conversation around one of my previous posts - &lt;a href=&quot;http://blogs.rupturedmonkey.com/?p=56&quot; rel=&quot;nofollow&quot;&gt;http://blogs.rupturedmonkey.com/?p=56&lt;/a&gt;
Thanks for the feedback
Nigel</description>
		<content:encoded><![CDATA[<p>Hi Ewan,<br />
I hear what your saying.&nbsp; sounds similar to the conversation around one of my previous posts &#8211; <a href="http://blogs.rupturedmonkey.com/?p=56" rel="nofollow">http://blogs.rupturedmonkey.com/?p=56</a><br />
Thanks for the feedback<br />
Nigel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ewan</title>
		<link>http://blog.nigelpoulton.com/self-tuning-storage/comment-page-1/#comment-179</link>
		<dc:creator>Ewan</dc:creator>
		<pubDate>Mon, 14 May 2007 11:39:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=85#comment-179</guid>
		<description>I don&#039;t really see why some storage vendors are putting so much complexity into tuning storage systems, personally I don&#039;t have time to work out how few ms per write is required for each system connected to our SAN, or how much cache should be allocated per drive.I just want to be able to say &quot;All drives attached to production environment A, high priority&quot;, and &quot;All drives attached to test environments B, C, D, low priority&quot;, then let the array sort itself out.Even a simple scale of priority from 1-10 would probably be too much, high medium and low would probably cover 90% of peoples requirements and need so much less effort from storage administrators everywhere.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t really see why some storage vendors are putting so much complexity into tuning storage systems, personally I don&#8217;t have time to work out how few ms per write is required for each system connected to our SAN, or how much cache should be allocated per drive.I just want to be able to say &quot;All drives attached to production environment A, high priority&quot;, and &quot;All drives attached to test environments B, C, D, low priority&quot;, then let the array sort itself out.Even a simple scale of priority from 1-10 would probably be too much, high medium and low would probably cover 90% of peoples requirements and need so much less effort from storage administrators everywhere.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

