Difference between revisions of "IOPs"
Jump to navigation
Jump to search
Line 18: | Line 18: | ||
* [[Making better decisions about Amazon RDS with Amazon CloudWatch metrics]] https://aws.amazon.com/blogs/database/making-better-decisions-about-amazon-rds-with-amazon-cloudwatch-metrics/ | * [[Making better decisions about Amazon RDS with Amazon CloudWatch metrics]] https://aws.amazon.com/blogs/database/making-better-decisions-about-amazon-rds-with-amazon-cloudwatch-metrics/ | ||
* [[DiskQueueDepth]] | * [[DiskQueueDepth]] | ||
+ | * [[EFS]] | ||
== See also == | == See also == |
Revision as of 06:33, 25 May 2023
- gp3: baseline performance of 3,000 IOPs and 125MB/s at any volume size, scale up to 16,000 IOPS and 1,000 MB/s for an additional fee
root_block_device argument in Terraform aws_instance resource
terraform show | grep -i iop iops = 0
News
- Nov 2022 gp3 https://aws.amazon.com/about-aws/whats-new/2022/11/amazon-rds-general-purpose-gp3-storage-volumes/ 3,000 IOPS baseline and up to 64,000 IOPS
Related
- Read IOPS
- Making better decisions about Amazon RDS with Amazon CloudWatch metrics https://aws.amazon.com/blogs/database/making-better-decisions-about-amazon-rds-with-amazon-cloudwatch-metrics/
- DiskQueueDepth
- EFS
See also
Advertising: