AWS ebs documentation change
Summary
Added guidance on maintaining optimal queue depth for provisioned IOPS volumes
Security assessment
The change provides performance optimization advice for maintaining consistent IOPS performance but does not address security vulnerabilities or introduce security features.
Diff
diff --git a/ebs/latest/userguide/ebs-io-characteristics.md b/ebs/latest/userguide/ebs-io-characteristics.md index b8d34638c..a7a3db594 100644 --- a//ebs/latest/userguide/ebs-io-characteristics.md +++ b//ebs/latest/userguide/ebs-io-characteristics.md @@ -60 +60 @@ Optimal queue length varies for each workload, depending on your particular appl -Transaction-intensive applications are sensitive to increased I/O latency and are well-suited for SSD-backed volumes. You can maintain high IOPS while keeping latency down by maintaining a low queue length and a high number of IOPS available to the volume. Consistently driving more IOPS to a volume than it has available can cause increased I/O latency. +Transaction-intensive applications are sensitive to increased I/O latency and are well-suited for SSD-backed volumes. You can maintain high IOPS while keeping latency down by maintaining a low queue length and a high number of IOPS available to the volume. Consistently driving more IOPS to a volume than it has available can cause increased I/O latency. For maximum consistency, a volume must maintain an average queue depth (rounded to the nearest whole number) of one for every 1,000 provisioned IOPS in a minute. For example, for a volume provisioned with 3,000 IOPS, the queue depth average must be 3.