Help us improve the AWS re:Post Knowledge Center by sharing your feedback in a brief survey. Your input can influence how we create and update our content to better support your AWS journey.
Can GP3 burst outside of the provisioned IOPS?
I am doing some testing on IOPS and Throughput and putting a GP3 volume under some stress using iometer.
The volume is 30GB, 3000 IOPS and 130MB/s throughput
However my observations in CloudWatch 1sec interval is the IOPS bursts up to 30,000 IOPS
My expectation is that it would have been capped at 3000 IOPS per the volume configuration.
- Newest
- Most votes
- Most comments
GP3 volumes are engineered to provide consistent performance without the ability to burst. As stated in the Amazon EBS documentation, GP3 volumes deliver a steady baseline IOPS performance of 3,000 IOPS, with the option to provision up to 16,000 IOPS for an additional fee. These volumes do not incorporate burst performance and are expected to consistently sustain their full provisioned IOPS and throughput performance.
The observed IOPS spikes up to 30,000 IOPS in CloudWatch could potentially be attributed to factors such as caching mechanisms, instance configurations, or measurement anomalies. It is advisable to review your testing environment thoroughly to ensure that there are no other variables influencing the performance metrics.
Reference: https://docs.aws.amazon.com/ebs/latest/userguide/general-purpose.html?form=MG0AV3
Please remember that Cloudwatch metrics are NOT realtime or instant metrics, but are always over a period of time that is 5 minutes by default or 1 minute if you enable detailed metrics. That means in your case that if you have e.g. detailed metrics enabled, your volume reached 30K IOPS over 1 Minutes that means 30.000/60 = 500 IOPS in average over the 1-min period.
Reference in our documentation here: https://docs.aws.amazon.com/ebs/latest/userguide/using_cloudwatch_ebs.html
Relevant content
- asked 3 years ago
