DB System Storage
The performance of MySQL HeatWave Service scales with the storage size selected for the DB system.
You cannot limit or edit the IOPS of the storage. You must provision the storage size based on your data size and performance requirements.
MySQL HeatWave Service uses the Block Volume service Higher Performance option over iSCSI. The final performance results may vary for different shapes and scenarios. It is recommended to perform benchmark analysis during your Proof of Concept testing to verify your environment configuration has adequate performance for your application requirements.
The storage throughput can also be limited by the maximum network bandwidth of the DB system's shape.
Initial storage size | Number of volumes | Maximum storage size |
Between 50-400 GB | 1 | 32 TB |
Between 401-800 GB | 2 | 64 TB |
Between 801-1,200 GB | 3 | 96 TB |
Between 1,201-1,600 GB | 4 | 128 TB |
Between 1,601-2,000 GB | 5 | 128 TB |
Between 2,001-2,400 GB | 6 | 128 TB |
Between 2,401-2,800 GB | 7 | 128 TB |
Between 2,801-3,200 GB | 8 | 128 TB |
Between 3,201-3,600 GB | 9 | 128 TB |
Between 3,601-4,000 GB | 10 | 128 TB |
Between 4,001-4,400 GB | 11 | 128 TB |
Between 4,401-4,800 GB | 12 | 128 TB |
Between 4,801-5,200 GB | 13 | 128 TB |
Between 5,201-5,600 GB | 14 | 128 TB |
Between 5,601-131,072 GB | 15 | 128 TB |
If you create a DB system with a small initial storage size and increase the storage size multiple times larger later, the storage performance could be limited by the less than optimal number of volumes.