 




<?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: New way of handling RAID 5?</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/new-way-of-handling-raid-5/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/new-way-of-handling-raid-5/</link>
	<description></description>
	<lastBuildDate>Wed, 22 May 2013 18:27:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: jjsmith</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/new-way-of-handling-raid-5/#comment-48418</link>
		<dc:creator>jjsmith</dc:creator>
		<pubDate>Mon, 31 Jan 2005 09:50:07 +0000</pubDate>
		<guid isPermaLink="false">#comment-48418</guid>
		<description><![CDATA[Write, or for that matter Read Cache does make a difference to performance. However Raid 5 and Raid 0+1 will always be different ( 0+1 better ). As a DBA I take this view, Raid 5 is &#039;cheaper&#039; than 0+1 ( byte for byte ). As customers want an ever increasing amount of data on-line people start to worry about hardware cost. So, if the data is important RAID 1, if I/O speed is important, add in RAID 0. If cost takes priority over performace and resilience that use RAID 5.
If you are the kind of DBA that it constantly being told to improve performance then stick with RAID 0+1 as &#039;you&#039; know exactly on which disk/spindle the data resides.
If in the future space comes under pressure and you need a stopgap solution, you can always change 0+1 to 5, but not the other way round.

Disk is so cheap now,that you should simply buy lots.

Regards
JJ]]></description>
		<content:encoded><![CDATA[<p>Write, or for that matter Read Cache does make a difference to performance. However Raid 5 and Raid 0+1 will always be different ( 0+1 better ). As a DBA I take this view, Raid 5 is &#8216;cheaper&#8217; than 0+1 ( byte for byte ). As customers want an ever increasing amount of data on-line people start to worry about hardware cost. So, if the data is important RAID 1, if I/O speed is important, add in RAID 0. If cost takes priority over performace and resilience that use RAID 5.<br />
If you are the kind of DBA that it constantly being told to improve performance then stick with RAID 0+1 as &#8216;you&#8217; know exactly on which disk/spindle the data resides.<br />
If in the future space comes under pressure and you need a stopgap solution, you can always change 0+1 to 5, but not the other way round.</p>
<p>Disk is so cheap now,that you should simply buy lots.</p>
<p>Regards<br />
JJ</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.044 seconds using memcached
Object Caching 267/273 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-22 23:02:56 -->