NetApp
Vserver : Policies > QoS Policies : Understanding QoS Policies : How the maximum throughput limit works
How the maximum throughput limit works
You can specify one service-level objective for a Storage QoS policy group: a maximum throughput limit. A maximum throughput limit, which you define in terms of IOPS or MB/s, specifies the throughput that the workloads in the policy group cannot collectively exceed.
When you specify a maximum throughput for a policy group, Storage QoS controls client operations to ensure that the aggregate throughput for all workloads in the policy group does not exceed the specified maximum throughput.
For example, you create the policy group "untested_apps" and specify a maximum throughput of 300 MB/s. You assign three volumes to the policy group. The aggregate throughput to those three volumes cannot exceed 300 MB/s.
Note: The aggregate throughput to the workloads in a policy group might exceed the specified limit by up to 10%. A deviation might occur if you have a workload that experiences rapid changes in throughput (sometimes called a "bursty workload").
Note the following about specifying a maximum throughput:
•
A throughput limit applies to all clients that access a storage object.
•
Do not set the limit too low, because you might underutilize the cluster.
•
Consider the minimum amount of throughput that you want to reserve for workloads that do not have limits.
For example, you can ensure that your critical workloads get the throughput that they need by limiting non-critical workloads.
•
You might want to provide room for growth.
For example, if you see an average utilization of 500 IOPS, you might specify a limit of 1,000 IOPS.

Was this topic helpful? Send comments to NetApp.