大网数据广告活动
服务器运维问答

Understanding EBSByteBalance% in AWS RDS gp3 volumes

· 52CE 我爱测

I am troubleshooting an AWS RDS Postgres instance that has been restarted by AWS several times in the last few days, very likely due to resource constraints. It's a testing DB that usually doesn't do much but we recently put some…

问题原文

原帖链接 · MoWo · CC BY-SA 4.0

I am troubleshooting an AWS RDS Postgres instance that has been restarted by AWS several times in the last few days, very likely due to resource constraints. It's a testing DB that usually doesn't do much but we recently put some higher load onto it. I found that the DB's EBS volume (200GB gp3) depleted its throughput credits and that the times of the DB restarts coincided pretty well with the EBSByteBalance% metric reaching zero. Then when the DB gets restarted, the volume apparently gets a fresh set of burst credits as can be seen in the screenshot below:

The credits now drop slightly slower as we have eased the load on the DB but they are still dropping. When I look at the current read and write throughput metrics, they seem to sum up to just about 5 to 7 MiB/s with occasional spikes:

Based on the information found here at Amazon RDS DB instance storage the baseline throughput for a gp3 volume below 400gb should be 125MiB/s. So can anyone help me explain why the EBSByteBalance% metric keeps decreasing in this scenario? Thanks!

已采纳解答

原帖链接 · MoWo · CC BY-SA 4.0

Okay, I followed @Tim's advice and contacted AWS support. They clarified the following:

Kindy be informed the metrics 'EBSIOBalance%' and 'EBSByteBalance%' are instance class metrics. Please note that GP3 volumes do not use burst performance, Hence the metrics refers to instance class burst performance and not volume. EBSIOBalance% monitors the instance I/O burst bucket, and EBSByteBalance% monitors the instance byte burst bucket. These metrics give information about the percentage of I/O or bytes credits remaining in the respective burst buckets. The metrics are expressed as a percentage, where 100% means that the instance has accumulated the maximum number of credits.

So what happened was that the T4G DB instance class also has an I/O and throughput limit that in our case was just around 10 MB/s. I was not aware of this and had a very hard time finding these performance numbers online. But for anyone wondering in the future they can be found here: https://instances.vantage.sh/rds/ They also confirmed that under resource constraints the RDS instance may reboot and see this as the obvious explanation for the behaviour we witnessed.

So the mystery is solved in our case. Hope this helps someone in the future

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2023-06-27)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。