Understanding RDS Database Behavior Post-Storage Type Change from io1 to gp3

1

We recently modified the storage type of one of our RDS databases from io1 with Provisioned IOPS (PIOP) of 3000 to gp3. Prior to this change, our read IOPS (Input/Output Operations Per Second) and read throughput metrics were stable and within expected ranges. However, since the switch, we've noticed significant spikes in these metrics, even though our traffic load has remained consistent with the levels we experienced last month.

This unexpected change is puzzling, and we're trying to understand the underlying reasons for these high values in read IOPS and throughput. To give you a clearer picture of the situation, I have attached screenshots of the metrics before and after the storage type change.

Could you please help us understand why we might be experiencing these spikes in read IOPS and throughput with the gp3 storage type? Any insights or recommendations you can provide would be greatly appreciated.

Attaching images related to ReadIOPS, ReadThroughPut, ReadLatency and CpuUtilization.

ReadIOPS ReadThroughPut ReadLatency CpuUtilization

1개 답변
1

Read IOPS are strictly a measurement of your workload, the volume type would have nothing to do with that metric.

AWS
중재자
philaws
답변함 4달 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인