<?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 Getting warning CPU TOO BUSY during dedupe in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Getting-warning-CPU-TOO-BUSY-during-dedupe/m-p/28786#M6644</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From my understanding SIS is like scrub where it uses as much free CPU as it can without interfering with your regular I/O. I don't really worry about CPU utilization, infact the higher it is the happier I am to be using more of what I'm paying for as long as it is not impacting clients.&amp;nbsp; On my 3020s I constantly see CPU jump to ~100% when SIS is running in addition to a scrub, but have not seen any impact to my clients from it.&amp;nbsp; One thing you should look at is latency during the time you are seeing this high CPU utilization.&amp;nbsp; If you are still serving out data at the same rate then CPU utilization doesn't really matter.&amp;nbsp; If you are seeing an impact to clients then definitely further investigation is needed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Aug 2011 21:39:09 GMT</pubDate>
    <dc:creator>vshevchuk</dc:creator>
    <dc:date>2011-08-05T21:39:09Z</dc:date>
    <item>
      <title>Getting warning CPU TOO BUSY during dedupe</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Getting-warning-CPU-TOO-BUSY-during-dedupe/m-p/28762#M6639</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello All&lt;/P&gt;&lt;P&gt;I was wondering if you guys are getting the same warning as I am with my FAS3240- CPU TOO BUSY @ 96%.&lt;/P&gt;&lt;P&gt;Currently, I have 3 volumes of 4TB hosting VMs. The warning usually occurs @midnight to 6am, this is also the same time dedupe is scheduled to run.&lt;/P&gt;&lt;P&gt;Is dedupe chewing up this much process? When the system is at this level, my VMs are crawling.&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;joey&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;﻿&lt;IMG src="http://community.netapp.com/legacyfs/online/11635_cpu.png" width="450" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:49:16 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Getting-warning-CPU-TOO-BUSY-during-dedupe/m-p/28762#M6639</guid>
      <dc:creator>joeycitrix</dc:creator>
      <dc:date>2025-06-05T06:49:16Z</dc:date>
    </item>
    <item>
      <title>Getting warning CPU TOO BUSY during dedupe</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Getting-warning-CPU-TOO-BUSY-during-dedupe/m-p/28766#M6640</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just curious - your graphs here show 90%+ CPU usage between around 5AM to 12PM, not between midnight and 6AM. Unless this is a timezone thing.... ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jul 2011 13:45:45 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Getting-warning-CPU-TOO-BUSY-during-dedupe/m-p/28766#M6640</guid>
      <dc:creator>rmharwood</dc:creator>
      <dc:date>2011-07-29T13:45:45Z</dc:date>
    </item>
    <item>
      <title>Getting warning CPU TOO BUSY during dedupe</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Getting-warning-CPU-TOO-BUSY-during-dedupe/m-p/28771#M6641</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are you running ONTAP 8 ? if yes what version exactly ?&lt;/P&gt;&lt;P&gt;There are a lot of bugs fixed in the most recent 8.0.1 Patch releases.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Niek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jul 2011 14:54:32 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Getting-warning-CPU-TOO-BUSY-during-dedupe/m-p/28771#M6641</guid>
      <dc:creator>vmsjaak13</dc:creator>
      <dc:date>2011-07-29T14:54:32Z</dc:date>
    </item>
    <item>
      <title>Getting warning CPU TOO BUSY during dedupe</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Getting-warning-CPU-TOO-BUSY-during-dedupe/m-p/28776#M6642</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No chance you are you are just hitting problems with backup and virus scanning?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you actually look at 'sis status -l' then you will see how long the actual sis processes run.&amp;nbsp; I don't think sis is doing this to a 3240... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 31 Jul 2011 21:14:43 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Getting-warning-CPU-TOO-BUSY-during-dedupe/m-p/28776#M6642</guid>
      <dc:creator>shaunjurr</dc:creator>
      <dc:date>2011-07-31T21:14:43Z</dc:date>
    </item>
    <item>
      <title>Getting warning CPU TOO BUSY during dedupe</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Getting-warning-CPU-TOO-BUSY-during-dedupe/m-p/28781#M6643</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;sis does this to my 2020 filer. But I would have thought a 3240 would have more juice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Although, it might be similar to a scrub where it uses as much CPU as it can if there is no other ongoing activity.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Aug 2011 10:15:20 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Getting-warning-CPU-TOO-BUSY-during-dedupe/m-p/28781#M6643</guid>
      <dc:creator>rwelshman</dc:creator>
      <dc:date>2011-08-01T10:15:20Z</dc:date>
    </item>
    <item>
      <title>Getting warning CPU TOO BUSY during dedupe</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Getting-warning-CPU-TOO-BUSY-during-dedupe/m-p/28786#M6644</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From my understanding SIS is like scrub where it uses as much free CPU as it can without interfering with your regular I/O. I don't really worry about CPU utilization, infact the higher it is the happier I am to be using more of what I'm paying for as long as it is not impacting clients.&amp;nbsp; On my 3020s I constantly see CPU jump to ~100% when SIS is running in addition to a scrub, but have not seen any impact to my clients from it.&amp;nbsp; One thing you should look at is latency during the time you are seeing this high CPU utilization.&amp;nbsp; If you are still serving out data at the same rate then CPU utilization doesn't really matter.&amp;nbsp; If you are seeing an impact to clients then definitely further investigation is needed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Aug 2011 21:39:09 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Getting-warning-CPU-TOO-BUSY-during-dedupe/m-p/28786#M6644</guid>
      <dc:creator>vshevchuk</dc:creator>
      <dc:date>2011-08-05T21:39:09Z</dc:date>
    </item>
  </channel>
</rss>

