<?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 instances requested for the nfsv3 object exceeds the data capacity of the performance subsystem in Software Development Kit (SDK) and API Discussions</title>
    <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/instances-requested-for-the-nfsv3-object-exceeds-the-data-capacity-of-the/m-p/127017#M2229</link>
    <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Trying to find out how to modify the maximum number os instances from an NFS performance query with ZAPI.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Call gets this error:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&amp;lt;results reason="Aggregated instances requested for the nfsv3 object exceeds the data capacity of the performance subsystem, because it includes 15552 constituent instances. With the current counter set, use the -node, -vserver, or -filter flags to include at most 6304 constituent instances in order to stay within the data capacity. Alternatively, requesting fewer counters will also reduce the required data and may allow more instances to be requested.resource limit exceeded" status="failed" errno="13001"/&amp;gt;&amp;lt;/netapp&amp;gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&amp;lt;results reason="Aggregated instances requested for the nfsv3 object exceeds the data capacity of the performance subsystem, because it includes 15552 constituent instances. With the current counter set, use the -node, -vserver, or -filter flags to include at most 6304 constituent instances in order to stay within the data capacity. Alternatively, requesting fewer counters will also reduce the required data and may allow more instances to be requested.resource limit exceeded" status="failed" errno="13001"/&amp;gt;&amp;lt;/netapp&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have read about a limit in the number of instances as a performance cap, or even to avoid time-outs, however I cannot confirm this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any engineering resources would be useful,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 16:10:08 GMT</pubDate>
    <dc:creator>Ken_Char</dc:creator>
    <dc:date>2025-06-04T16:10:08Z</dc:date>
    <item>
      <title>instances requested for the nfsv3 object exceeds the data capacity of the performance subsystem</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/instances-requested-for-the-nfsv3-object-exceeds-the-data-capacity-of-the/m-p/127017#M2229</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Trying to find out how to modify the maximum number os instances from an NFS performance query with ZAPI.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Call gets this error:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&amp;lt;results reason="Aggregated instances requested for the nfsv3 object exceeds the data capacity of the performance subsystem, because it includes 15552 constituent instances. With the current counter set, use the -node, -vserver, or -filter flags to include at most 6304 constituent instances in order to stay within the data capacity. Alternatively, requesting fewer counters will also reduce the required data and may allow more instances to be requested.resource limit exceeded" status="failed" errno="13001"/&amp;gt;&amp;lt;/netapp&amp;gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&amp;lt;results reason="Aggregated instances requested for the nfsv3 object exceeds the data capacity of the performance subsystem, because it includes 15552 constituent instances. With the current counter set, use the -node, -vserver, or -filter flags to include at most 6304 constituent instances in order to stay within the data capacity. Alternatively, requesting fewer counters will also reduce the required data and may allow more instances to be requested.resource limit exceeded" status="failed" errno="13001"/&amp;gt;&amp;lt;/netapp&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have read about a limit in the number of instances as a performance cap, or even to avoid time-outs, however I cannot confirm this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any engineering resources would be useful,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 16:10:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/instances-requested-for-the-nfsv3-object-exceeds-the-data-capacity-of-the/m-p/127017#M2229</guid>
      <dc:creator>Ken_Char</dc:creator>
      <dc:date>2025-06-04T16:10:08Z</dc:date>
    </item>
    <item>
      <title>Re: instances requested for the nfsv3 object exceeds the data capacity of the performance subsystem</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/instances-requested-for-the-nfsv3-object-exceeds-the-data-capacity-of-the/m-p/127084#M2233</link>
      <description>&lt;P&gt;Just to be clear, you're making a single call to&amp;nbsp;perf-object-get-instances and it's wanting to return 15k+ results, which is leading to the error?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any way you can break the request into multiple and aggregate the results on the client side? &amp;nbsp;For example, target each SVM, or volumes starting with each letter of the alphabet?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Andrew&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jan 2017 21:42:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/instances-requested-for-the-nfsv3-object-exceeds-the-data-capacity-of-the/m-p/127084#M2233</guid>
      <dc:creator>asulliva</dc:creator>
      <dc:date>2017-01-17T21:42:31Z</dc:date>
    </item>
  </channel>
</rss>

