CPU over-subscription leads to QoS minimum latency
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