<?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 What is the RAID-DP write penalty in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/What-is-the-RAID-DP-write-penalty/m-p/91727#M19373</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am just looking for more accurate information around RAID-DP write penalty. I know that most folks at NetApp or NetApp consultants elsewhere would immediately say - 1 to 2 maximum. That's b'cos WAFL turns incoming radom IOs into sequential full stripes. That's understood, but is that an&amp;nbsp;average figure of both during low storage utilization &amp;amp; high storage utilization ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would&amp;nbsp;be really happy if&amp;nbsp;someone can share more information around this, during:&lt;BR /&gt;1. Low utilization of storage&lt;BR /&gt;2. High utilization of storage&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. During low utiliztion of storage - WAFL collects logically random writes and turns them into physical full sequential writes, as a result of which, it calculates the parity in the meomory on the fly, that means write penalty of maximum 2.&lt;/P&gt;&lt;P&gt;2. During High utilization of storage - What if my aggregate is 95%, and I have fragmented spaces, free full stripes are out of question, club this with back-2-back CPs. WAFL have to read the 'on disk blocks' to re-calculate the Parity and then write the new stripe. Does this mean, during times like that, we could see write IO penalty going up to 4.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope&amp;nbsp;to hear&amp;nbsp;some thoughts around this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;-Ashwin&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2025 05:27:37 GMT</pubDate>
    <dc:creator>ASHWINPAWARTESL</dc:creator>
    <dc:date>2025-06-05T05:27:37Z</dc:date>
    <item>
      <title>What is the RAID-DP write penalty</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/What-is-the-RAID-DP-write-penalty/m-p/91727#M19373</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am just looking for more accurate information around RAID-DP write penalty. I know that most folks at NetApp or NetApp consultants elsewhere would immediately say - 1 to 2 maximum. That's b'cos WAFL turns incoming radom IOs into sequential full stripes. That's understood, but is that an&amp;nbsp;average figure of both during low storage utilization &amp;amp; high storage utilization ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would&amp;nbsp;be really happy if&amp;nbsp;someone can share more information around this, during:&lt;BR /&gt;1. Low utilization of storage&lt;BR /&gt;2. High utilization of storage&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. During low utiliztion of storage - WAFL collects logically random writes and turns them into physical full sequential writes, as a result of which, it calculates the parity in the meomory on the fly, that means write penalty of maximum 2.&lt;/P&gt;&lt;P&gt;2. During High utilization of storage - What if my aggregate is 95%, and I have fragmented spaces, free full stripes are out of question, club this with back-2-back CPs. WAFL have to read the 'on disk blocks' to re-calculate the Parity and then write the new stripe. Does this mean, during times like that, we could see write IO penalty going up to 4.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope&amp;nbsp;to hear&amp;nbsp;some thoughts around this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;-Ashwin&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:27:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/What-is-the-RAID-DP-write-penalty/m-p/91727#M19373</guid>
      <dc:creator>ASHWINPAWARTESL</dc:creator>
      <dc:date>2025-06-05T05:27:37Z</dc:date>
    </item>
  </channel>
</rss>

