4.3.2. IOPS limits that scale according to volume size
You can create IOPS volume performance limits that are determined by the capacity of the volumes that your users create. These Quality of Service (QoS) limits scale with the size of the provisioned volumes. For example, if the volume type has an IOPS limit of 500 per GB of volume size for read operations, then a provisioned 3 GB volume of this volume type would have a read IOPS limit of 1500.
- Considerations
- The size of the volume is determined when the volume is attached to an instance. If the size of the volume is changed while it is attached to an instance, these limits are only recalculated for the new volume size when this volume is detached and then reattached to an instance.
- Instead of using a total limit you can apply separate limits to the read and write operations or choose to limit only the read or write operations.
- Read and write limits are ignored when you specify a total limit.
-
The consumer of the QoS specification containing these QoS limits can either be
front-endorboth, but notback-end. For more information, see Consumers of Block Storage QoS specifications.
You can use the following QoS property keys, specified in IOPS per GB, to create scalable volume performance limits:
-
total_iops_sec_per_gb: Specify a global IOPS limit per GB of volume size for both the read and write operations. -
read_iops_sec_per_gb: Specify a IOPS limit per GB of volume size that only applies to the read operations. -
write_iops_sec_per_gb: Specify a IOPS limit per GB of volume size that only applies to the write operations.