<?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 Write latency in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Write-latency/m-p/41778#M2922</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Frndz,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We had a huge write latency( approx 200 msecs) in all volumes of a specific SAS aggr, let's say aggr1 .Its having a 47 disks with 3 RG -16,16,15 .&lt;/P&gt;&lt;P&gt;Aggr IOPS &amp;amp; Volume IOPS are very low been around 150 .&lt;/P&gt;&lt;P&gt;CPU Utilization was normal being 50% ---Is there any way to calculate the NVRAM usage ? as its a write latency i suspect perhaps it could be any reason.&lt;/P&gt;&lt;P&gt;Can anyone guide me, what are the areas i need to check /look to mitigate this ?&lt;/P&gt;&lt;P&gt;More over i don't believe it could be a loop saturation since its a SAS loop ,anyone correct me if&amp;nbsp; i wrong.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;Saran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 06:15:35 GMT</pubDate>
    <dc:creator>saranraj456</dc:creator>
    <dc:date>2025-06-05T06:15:35Z</dc:date>
    <item>
      <title>Write latency</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Write-latency/m-p/41778#M2922</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Frndz,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We had a huge write latency( approx 200 msecs) in all volumes of a specific SAS aggr, let's say aggr1 .Its having a 47 disks with 3 RG -16,16,15 .&lt;/P&gt;&lt;P&gt;Aggr IOPS &amp;amp; Volume IOPS are very low been around 150 .&lt;/P&gt;&lt;P&gt;CPU Utilization was normal being 50% ---Is there any way to calculate the NVRAM usage ? as its a write latency i suspect perhaps it could be any reason.&lt;/P&gt;&lt;P&gt;Can anyone guide me, what are the areas i need to check /look to mitigate this ?&lt;/P&gt;&lt;P&gt;More over i don't believe it could be a loop saturation since its a SAS loop ,anyone correct me if&amp;nbsp; i wrong.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;Saran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:15:35 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Write-latency/m-p/41778#M2922</guid>
      <dc:creator>saranraj456</dc:creator>
      <dc:date>2025-06-05T06:15:35Z</dc:date>
    </item>
    <item>
      <title>Re: Write latency</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Write-latency/m-p/41782#M2924</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ideally gather a perfstat and send to NetApp support, but for a quick check in the meantime...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During the period of high latency, run a sysstat -x 1 on the console.&amp;nbsp; Firstly look at the 'CP ty' column, watch out for any 'B' or (worse) 'b'.&amp;nbsp; This suggests your NVRAM is not big enough, or you're not flushing data to disk fast enough (busy disks).&amp;nbsp; Also for a rough disk utilisation figure, check the 'Disk Util' column to see how busy the busiest disk on the system is.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the problem is NVRAM being full ('B' or 'b') you would normally expect ALL write workloads on the filer to be affected, not just those on the affected aggr.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To see how busy the disks are, you can use statit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Craig&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Nov 2012 10:31:38 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Write-latency/m-p/41782#M2924</guid>
      <dc:creator>GARDINEC_EBRD</dc:creator>
      <dc:date>2012-11-08T10:31:38Z</dc:date>
    </item>
  </channel>
</rss>

