Skip to main content
NetApp Knowledge Base

How to measure CPU utilization

Views:
16,791
Visibility:
Public
Votes:
17
Category:
clustered-data-ontap-8
Specialty:
perf
Last Updated:

Applies to

  • ONTAP 9

Answer

As part of a holistic view of the system, use the command line to view CPU utilization in real-time:

Note: The CPU domains are listed in the article CPU as a compute resource and the CPU domains explained in ONTAP 9

Verify the CPU utilization with the following commands : 

  1. Using sysstat -M 1

netapp::> set diag
Warning: These diagnostic commands are for use by NetApp personnel only.
Do you want to continue? {y|n}: y
netapp::*> node run -node netapp-01 sysstat -M 1
ANY1+ ANY2+ ANY3+ ANY4+ ANY5+ ANY6+ ANY7+ ANY8+ ANY9+ ANY10+ ANY11+ ANY12+ ANY13+ ANY14+ ANY15+ ANY16+  AVG 
 100%  100%  100%   99%   98%   96%   94%   91%   86%    81%    76%    70%    64%    57%    48%   37%   81%

CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 CPU8 CPU9 CPU10 CPU11 CPU12 CPU13 CPU14 CPU15 
 78%  76%  77%  83%  82%  83%  82%  82%  82%  82%   83%   84%   83%   82%   83%   82% 

Nwk_Excl Nwk_Lg Nwk_Exmpt Protocol Cluster Storage Raid Raid_Ex Target Kahuna WAFL_Ex(Kahu)
      3%     2%      450%       0%      0%     49%   2%    136%     0%     4%    511%( 94%) 

WAFL_XClean SM_Exempt Cifs Exempt SSAN_Ex Intr Host  Ops/s   CP
         0%        0%   0%   112%      0%  28%   8%  47111   0%

In the above example, Average CPU Utilization is 81% across the 16 cores.  

Busiest domains:

  • WAFL exempt at 511%
  • Networking exempt at 450%
  • RAID exempt at 136%, and exempt at 112%.
  • WAFL was active 98% of the sample interval, with 4% spent in serial processing and 94% in parallel processing. 
  • WAFL serial processing being quite low, it is likely that more work could be completed by parallelized WAFL
  • Being 98% active within the sample interval is not a concern without other contributing performance indicators.
  • Overall CPU resources get scarce, increasing the likelihood of work queuing for CPU, potentially impacting client latency.
  1. Using sysstat - x 1 

cluster1::> set diag
Warning: These diagnostic commands are for use by NetApp personnel only.
Do you want to continue? {y|n}: y
cluster1::*> node run -node cluster1-01 sysstat -x 1
 CPU    NFS   CIFS   HTTP   Total     Net   kB/s    Disk   kB/s    Tape   kB/s   Cache  Cache    CP 
                                       in    out    read  write    read  write     age    hit  time 
  2%      0      0      0      24       7      7      12       0       0      0   >60    100%    0% 
  2%      0      0      0       5      11      4       0      24       0      0   >60    100%    0% 
  4%      0      0      0       0       9      9      20    1274       0      0   >60    100%    1% 
  4%      0      0      0       3       7      8      12      36       0      0   >60      -     0% 
  1%      0      0      0       1       4      5       0       0       0      0   >60    100%    0% 
  2%      0      0      0      20       6      5       0       0       0      0   >60      -     0% 
  5%      0      0      0       8       5      6      12      24       0      0   >60      -     0% 
  1%      0      0      0       0      12     13      12       0       0      0   >60      -     0% 
  2%      0      0      0       0       3      4       0      36       0      0   >60      -     0% 

 

In the above example, CPU Utilization can be viewed from the first column which is 2%.

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.