topic CPU Concurrency of 1+ CPU on AFF-A300 with ONTAP 9.1P13 in ONTAP Discussions

CPU Concurrency of 1+ CPU on AFF-A300 with ONTAP 9.1P13

Ontapforrum — Wed, 04 Jun 2025 12:49:03 GMT

Hi,

According to this KB all these 'Domains' has CPU Concurrency of 1+ CPUs:

https://kb.netapp.com/app/answers/answer_view/a_id/1001217

Host os : 1+
exempt : 1+
SM_Exempt : 1+ [No SnapMirror configured yet]
WAFL_XCleaner : 1+
WAFL_EX : 1+
ssan_exempt : 1+ [No FCP/iSCSI processing, Pure NFS environment]
XO_Ex : 1+
raid_exempt : 1+
storage : 1+

nwk_exempt: 1+ [IP & NFS Processing]

My question:
Given a situation, where all the above domains except (SM_Exempt & ssan_exempt) are running parallely and are able to process information using single CPU. So, total '7' CPU are being used at a given time.

For a NetApp FILER such as AFF-A300: 16 Cores [16-7=9]

My question : If need be, will 'nwk_exempt' domain be able to maximum it's processing using all the available CPU cores ? Or there is a limit to, it can grab ?, given they are indeed available.

@Alex Dawson : Do you mind attending to this query, you have been very helpful in the past on this subject.

Thanks,
-Ash

Re: CPU Concurrency of 1+ CPU on AFF-A300 with ONTAP 9.1P13

AlexDawson — Mon, 25 Feb 2019 04:59:15 GMT

Hi there,

This veers too far into our trade secrets to discuss publicly.

Please log a support ticket outlining your performance concern, provide me the ticket number, and I will ensure it gets dealt with appropriately.

Thanks!

Re: CPU Concurrency of 1+ CPU on AFF-A300 with ONTAP 9.1P13

Ontapforrum — Mon, 25 Feb 2019 09:43:45 GMT

Hi Alex,

Thanks for your reply. I totally understand it, and yes I realzied this after posting the query.

Regards,

-Ash

Re: CPU Concurrency of 1+ CPU on AFF-A300 with ONTAP 9.1P13

Ontapforrum — Thu, 28 Feb 2019 13:53:58 GMT

Just wanted to add a bit of information here:

CSMP domain scheduling logic and domain grabbing is unique to ONTAP ,obviously that's the proprietary info. But, the following command is quite useful in understanding 'domain' busy/processor info:

set diag [ Under diag : more options show up for processor related counter]

statistics start -object processor -counter domain_busy -sample-id [1..100] example : 2
statistics stop -sample-id 2
statistics show -object processor -counter domain_busy