Skip to main content
NetApp Knowledge Base

How to identify a bursty or oversubscribed workload causing QoS latency

Views:
1,341
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
perf
Last Updated:

Applies to

ONTAP 9

Description

  • It may appear QoS is throttling below policy limits due to a bursty workload
  • A bursty workload may only run for part of a second or a few seconds
    • Example: Active IQ Unified Manager averages statistics in 5 minutes so if a workload only runs a minute at the maximum, it may look like premature throttling
  • This article discusses how to determine if a bursty workload is causing premature QoS latency.

 

 

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.