<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Raid ADG stripe size in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/raid-adg-stripe-size/m-p/3616081#M17416</link>
    <description>I would like to know why to use RAID ADG instead of RAID 5 with spare. To prevent two exactly simultaneous disk failures?&lt;BR /&gt;&lt;BR /&gt;I prefer RAID 5 with spare for performance.&lt;BR /&gt;&lt;BR /&gt;The stripe size depends of the data type to be stored on the disk.&lt;BR /&gt;&lt;BR /&gt;A large chunk size (relative to the average request size) increases the request rate&lt;BR /&gt;by enabling multiple disk drives to respond to multiple requests.&lt;BR /&gt;&lt;BR /&gt;Large chunk sizes also tend to increase the performance of random reads and&lt;BR /&gt;writes. HP recommends that you use a chunk size of 10 to 20 times the average&lt;BR /&gt;request size, rounded to the closest prime number. RAID 5 sets intended for high&lt;BR /&gt;data rate performance should use a relatively large number&lt;BR /&gt;&lt;BR /&gt;RAID 0 and RAID 0+1 sets intended for high data transfer rates should use a&lt;BR /&gt;relatively low chunk size. If you have mostly sequential reads or writes (like those needed to work with&lt;BR /&gt;large graphic files), make the chunk size for RAID 0 and RAID 0+1 a small&lt;BR /&gt;number.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 31 Aug 2005 15:25:24 GMT</pubDate>
    <dc:creator>Ivan Ferreira</dc:creator>
    <dc:date>2005-08-31T15:25:24Z</dc:date>
    <item>
      <title>Raid ADG stripe size</title>
      <link>https://community.hpe.com/t5/disk-enclosures/raid-adg-stripe-size/m-p/3616080#M17415</link>
      <description>What is the optimal stripe size using RAID ADG on MSA 500 G2 Disk Array?</description>
      <pubDate>Wed, 31 Aug 2005 14:46:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/raid-adg-stripe-size/m-p/3616080#M17415</guid>
      <dc:creator>Luke LaFebre_1</dc:creator>
      <dc:date>2005-08-31T14:46:33Z</dc:date>
    </item>
    <item>
      <title>Re: Raid ADG stripe size</title>
      <link>https://community.hpe.com/t5/disk-enclosures/raid-adg-stripe-size/m-p/3616081#M17416</link>
      <description>I would like to know why to use RAID ADG instead of RAID 5 with spare. To prevent two exactly simultaneous disk failures?&lt;BR /&gt;&lt;BR /&gt;I prefer RAID 5 with spare for performance.&lt;BR /&gt;&lt;BR /&gt;The stripe size depends of the data type to be stored on the disk.&lt;BR /&gt;&lt;BR /&gt;A large chunk size (relative to the average request size) increases the request rate&lt;BR /&gt;by enabling multiple disk drives to respond to multiple requests.&lt;BR /&gt;&lt;BR /&gt;Large chunk sizes also tend to increase the performance of random reads and&lt;BR /&gt;writes. HP recommends that you use a chunk size of 10 to 20 times the average&lt;BR /&gt;request size, rounded to the closest prime number. RAID 5 sets intended for high&lt;BR /&gt;data rate performance should use a relatively large number&lt;BR /&gt;&lt;BR /&gt;RAID 0 and RAID 0+1 sets intended for high data transfer rates should use a&lt;BR /&gt;relatively low chunk size. If you have mostly sequential reads or writes (like those needed to work with&lt;BR /&gt;large graphic files), make the chunk size for RAID 0 and RAID 0+1 a small&lt;BR /&gt;number.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Aug 2005 15:25:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/raid-adg-stripe-size/m-p/3616081#M17416</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-08-31T15:25:24Z</dc:date>
    </item>
  </channel>
</rss>

