For the most recent update on ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1), refer to the AWS Health Dashboard. For information on AWS Service migration, see How do I migrate my services to another region?
How do I troubleshoot a low burst balance value in my Amazon RDS for PostgreSQL DB instance?
I want to troubleshoot a low burst balance in my Amazon Relational Database Service (Amazon RDS) for PostgreSQL DB instance.
Resolution
Amazon RDS DB instances use Amazon Elastic Block Store (Amazon EBS) volumes for storage. When Amazon RDS depletes the burst balance of a volume, the volume returns to its baseline performance values. The volume stays at its baseline until input/output operations per second (IOPS) use is lower than the baseline. Then, the burst balance starts to refill.
Based on the amount of storage you request, Amazon RDS automatically stripes across multiple Amazon EBS volumes to enhance performance.
To identify the number of volumes for a DB instance, turn on Enhanced Monitoring and check the number of volumes in the Amazon Aurora and RDS console.
Troubleshoot a low burst balance value
Take the following actions:
- To check if you must optimize your SQL queries, turn on Standard mode of Database Insights for Amazon RDS.
- Determine whether you need to increase the DB instance storage size to achieve a higher IOPS capacity.
Note: You can't reduce your storage amount after Amazon RDS allocates storage. Increase your storage capacity only after you verify all other tuning options. - Scale up your storage class to improve performance. Or, change the storage type from General Purpose SSD (gp2) volumes to provisioned SSD (io1) volumes and assign the required IOPS. Specify the amount of storage that you want to allocate. Then, specify the amount of dedicated IOPS that you want.
- If you see IOPS or throughput throttle on a DB instance, then scale up the instance class to get a higher throughput or IOPS capacity.
Troubleshoot enhanced modeling for micro-bursting
For more information about micro-bursting in EBS volumes, see How do I troubleshoot the latency of Amazon EBS volumes caused by an IOPS bottleneck in my Amazon RDS instance? Review the Micro-bursting section.
Related information
Understanding burst vs. baseline performance with Amazon RDS and gp2
- Language
- English
To identify the number of volumes for an RDS instance, turn on Enhanced Monitoring and check the number of volumes in the Physical Devices console.
If, like me, you have no idea how to do this, I think the way is to go to your DB in RDS, go to the Monitoring tab, then click the dropdown there to go to Enhanced Monitoring (assuming you have it turned on).
Then, I think you can select a graph to see how many physical devices you have (in my case, it appeared to be four).
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Relevant content
- asked 4 years ago
