<?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: Iâ€™ll make that decision thanks!</title>
	<atom:link href="http://blog.nigelpoulton.com/ill-make-that-decision-thanks/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nigelpoulton.com/ill-make-that-decision-thanks/#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/ill-make-that-decision-thanks/comment-page-1/#comment-108</link>
		<dc:creator>Chris M Evans</dc:creator>
		<pubDate>Tue, 19 Dec 2006 20:59:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=58#comment-108</guid>
		<description>EMC were well behind on RAID5, they (I believe) are about to do RAID6 on their Symmetrix range, but no plans on the cheap and nasty (sorry, I mean Clariion) storage.  Shame, that&#039;s where I&#039;d be wanting it - 500 or 750GB &quot;dodgy&quot; SATA drives....Give me HDS and RAID 6 any day.</description>
		<content:encoded><![CDATA[<p>EMC were well behind on RAID5, they (I believe) are about to do RAID6 on their Symmetrix range, but no plans on the cheap and nasty (sorry, I mean Clariion) storage.  Shame, that&#8217;s where I&#8217;d be wanting it &#8211; 500 or 750GB &#8220;dodgy&#8221; SATA drives&#8230;.Give me HDS and RAID 6 any day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SanGod</title>
		<link>http://blog.nigelpoulton.com/ill-make-that-decision-thanks/comment-page-1/#comment-107</link>
		<dc:creator>SanGod</dc:creator>
		<pubDate>Sat, 16 Dec 2006 05:29:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=58#comment-107</guid>
		<description>EMC has a very bad habit of trying to take the management away where it counts, but the funny part is that I&#039;ve seen more people do more damage trying to take the management away from EMC than not.

There are a number of instances with EMC where it is in fact best to let the Symm place data.  IE don&#039;t spend too much effort on where the data is on the back-end of the array, if you were paying attention and bought optimizer, it&#039;s a moot point anyway.

When you&#039;re forming metadevices (stripe-sets) it&#039;s best to *NOT* let EMC decide where the devices are, as if you tell it to create a 10-way metavolume without specifying which volumes to include, it will scatter them across the array.  While you might get a slight (and I mean *VERY* slight) improvement in performance, it doesn&#039;t make up for the hellishness of having meta-members scattered all over the array.

Again, buy optimizer, it&#039;s a small price to pay, and lay out the hypervolumes sequentially, which almost assures you won&#039;t have any back-end contention.  (As a function of the Enginuity code is to spread wide across the back-end as a default)</description>
		<content:encoded><![CDATA[<p>EMC has a very bad habit of trying to take the management away where it counts, but the funny part is that I&#8217;ve seen more people do more damage trying to take the management away from EMC than not.</p>
<p>There are a number of instances with EMC where it is in fact best to let the Symm place data.  IE don&#8217;t spend too much effort on where the data is on the back-end of the array, if you were paying attention and bought optimizer, it&#8217;s a moot point anyway.</p>
<p>When you&#8217;re forming metadevices (stripe-sets) it&#8217;s best to *NOT* let EMC decide where the devices are, as if you tell it to create a 10-way metavolume without specifying which volumes to include, it will scatter them across the array.  While you might get a slight (and I mean *VERY* slight) improvement in performance, it doesn&#8217;t make up for the hellishness of having meta-members scattered all over the array.</p>
<p>Again, buy optimizer, it&#8217;s a small price to pay, and lay out the hypervolumes sequentially, which almost assures you won&#8217;t have any back-end contention.  (As a function of the Enginuity code is to spread wide across the back-end as a default)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: snig</title>
		<link>http://blog.nigelpoulton.com/ill-make-that-decision-thanks/comment-page-1/#comment-106</link>
		<dc:creator>snig</dc:creator>
		<pubDate>Thu, 14 Dec 2006 19:55:29 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=58#comment-106</guid>
		<description>Well how long did it take EMCÂ² to move away from RAID-S and go to true RAID-5?  Many many years...</description>
		<content:encoded><![CDATA[<p>Well how long did it take EMCÂ² to move away from RAID-S and go to true RAID-5?  Many many years&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

