Skip to main content
NetApp Knowledge Base

CPU over-subscription leads to QoS minimum latency and user slowness

  1. Last updated
  2. Save as PDF
Views:
404
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
perf
Last Updated:

Applies to

ONTAP 9.7+

Issue

QoS latency is observed for workloads utilizing QoS floors or adaptive QoS and the nodes hosting the workloads are experiencing a CPU bottleneck.
 
To check if a node is experiencing a CPU bottleneck, the following command can be used:
 
cluster::> system node run -node -command sysstat -x 1
 
To check if the latency is due to QoS minimums, the following command can be used:
 
cluster::> qos statistics volume latency show -volume VOLUME_NAME -vserver VSERVER_NAME
 
The majority of latency will be observed under the column labeled Qos Min

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.