Starting from November 29, 2024, the maximum IOPS for ApsaraDB RDS for MySQL instances that use local disks will be increased up to 150,000. You are not charged additional fees for the increase of the maximum IOPS.
Background information
With the continuous evolution of ApsaraDB RDS, the maximum IOPS of ApsaraDB RDS for MySQL instances that use local disks increases up to 150,000.
Applicable scope
All primary RDS for MySQL instances that use local disks. For more information, see Instance types for standard primary ApsaraDB RDS for MySQL instances (original x86 architecture).
All read-only RDS for MySQL instances that use local disks. For more information, see Instance types for standard read-only ApsaraDB RDS for MySQL instances (original x86 architecture).
This change of the maximum IOPS does not apply to RDS for MySQL instances of phased-out instance types. We recommend that you change the instance types of your instances to avaiable instance types. For more information about how to change instance types, see Change instance specifications.
Effective date and method
Starting from November 29, 2024, the maximum IOPS of RDS for MySQL instances that use local disks is increased in the following two ways:
Newly-purchased instances: The maximum IOPS is automatically increased.
Existing instances: The maximum IOPS is not automatically increased. It is increased only when you manually restart the instance ro change the specifications of the instance. For more information, see Restart an ApsaraDB RDS instance and Change instance specifications.
Usage notes
If you restart an existing instance to make the increase of maximum IOPS take effect, the instance is unavaible for about 30 seconds. We recommend that you restart your instance during off-peak hours and make sure that your application can automatically reconnect to the instance after the restart.
You can log on to the ApsaraDB RDS console to confirm whether the maximum IOPS of your instance is increased by performing the following steps: On the Instances page, click the instance ID. On the Basic Information tab of the instance details page, view the value of Maximum IOPS in the Configuration Information section.
The increase of the maximum IOPS results in the decrease of IOPS usage based on following formula:
IOPS usage = Actually used IOPS / Instance maximum IOPS. Therefore, you do not need to worry about the sudden IOPS usage decrease of your instance after the maximum IOPS is increased.
Maximum IOPS before and after the adjustment
The following table compares the maximum IOPS of RDS for MySQL instances of different instance types before and after the adjustment.
Primary instance types
Instance family | Instance type | Number of CPU cores and memory capacity | Maximum IOPS before adjustment | Maximum IOPS after adjustment |
General-purpose instance family | rds.mysql.t1.small | 1 core, 1 GB | 600 | 1,200 |
rds.mysql.s1.small | 1 core, 2 GB | 1,000 | 2,000 | |
rds.mysql.s2.large | 2 cores, 4 GB | 2,000 | 4,000 | |
rds.mysql.s2.xlarge | 2 cores, 8 GB | 4,000 | 6,000 | |
rds.mysql.s3.large | 4 cores, 8 GB | 5,000 | 8,000 | |
rds.mysql.m1.medium | 4 cores, 16 GB | 7,000 | 14,000 | |
rds.mysql.c1.large | 8 cores, 16 GB | 8,000 | 20,000 | |
rds.mysql.c1.xlarge | 8 cores, 32 GB | 12,000 | 28,000 | |
rds.mysql.c2.xlarge | 16 cores, 64 GB | 14,000 | 40,000 | |
rds.mysql.c2.xlp2 | 16 cores, 96 GB | 16,000 | 40,000 | |
Dedicated instance family | mysql.x4.large.2 | 4 cores, 16 GB | 4,500 | 30,000 |
mysql.x4.xlarge.2 | 8 cores, 32 GB | 9,000 | 45,000 | |
mysql.x4.2xlarge.2 | 16 cores, 64 GB | 18,000 | 60,000 | |
mysql.x4.4xlarge.2 | 32 cores, 128 GB | 36,000 | 80,000 | |
mysql.x4.8xlarge.2 | 64 cores, 256 GB | 72,000 | 150,000 | |
mysql.x8.medium.2 | 2 cores, 16 GB | 4,500 | 15,000 | |
mysql.x8.large.2 | 4 cores, 32 GB | 9,000 | 40,000 | |
mysql.x8.xlarge.2 | 8 cores, 64 GB | 18,000 | 50,000 | |
mysql.x8.2xlarge.2 | 16 cores, 128 GB | 36,000 | 60,000 | |
mysql.x8.4xlarge.2 | 32 cores, 256 GB | 72,000 | 100,000 | |
mysql.x8.8xlarge.2 | 64 cores, 512 GB | 144,000 | 150,000 | |
Dedicated host instance family | rds.mysql.st.h43 | 60 cores, 470 GB | 120,000 | 150,000 |
rds.mysql.st.v52 | 90 cores, 720 GB | 140,000 | 150,000 |
Read-only instance types
Instance family | Instance type | Number of CPU cores and memory capacity | Maximum IOPS before adjustment | Maximum IOPS after adjustment |
General-purpose instance family | rds.mysql.t1.small | 1 core, 1 GB | 600 | 1,200 |
rds.mysql.s1.small | 1 core, 2 GB | 1,000 | 2,000 | |
rds.mysql.s2.large | 2 cores, 4 GB | 2,000 | 4,000 | |
rds.mysql.s2.xlarge | 2 cores, 8 GB | 4,000 | 6,000 | |
rds.mysql.s3.large | 4 cores, 8 GB | 5,000 | 8,000 | |
rds.mysql.m1.medium | 4 cores, 16 GB | 7,000 | 14,000 | |
rds.mysql.c1.large | 8 cores, 16 GB | 8,000 | 20,000 | |
rds.mysql.c1.xlarge | 8 cores, 32 GB | 12,000 | 28,000 | |
rds.mysql.c2.xlarge | 16 cores, 64 GB | 14,000 | 40,000 | |
rds.mysql.c2.xlp2 | 16 cores, 96 GB | 16,000 | 40,000 | |
Dedicated instance family | mysqlro.x4.large.1 | 4 cores, 16 GB | 4,500 | 30,000 |
mysqlro.x4.xlarge.1 | 8 cores, 32 GB | 9,000 | 45,000 | |
mysqlro.x4.2xlarge.1 | 16 cores, 64 GB | 18,000 | 60,000 | |
mysqlro.x4.4xlarge.1 | 32 cores, 128 GB | 36,000 | 80,000 | |
mysqlro.x4.8xlarge.1 | 64 cores, 256 GB | 72,000 | 150,000 | |
mysqlro.x8.medium.1 | 2 cores, 16 GB | 4,500 | 15,000 | |
mysqlro.x8.large.1 | 4 cores, 32 GB | 9,000 | 40,000 | |
mysqlro.x8.xlarge.1 | 8 cores, 64 GB | 18,000 | 50,000 | |
mysqlro.x8.2xlarge.1 | 16 cores, 128 GB | 36,000 | 60,000 | |
mysqlro.x8.4xlarge.1 | 32 cores, 256 GB | 72,000 | 100,000 | |
mysqlro.x8.8xlarge.1 | 64 cores, 512 GB | 144,000 | 150,000 | |
Dedicated host instance family | rds.mysql.st.h43 | 60 cores, 470 GB | 120,000 | 150,000 |
rds.mysql.st.v52 | 90 cores, 720 GB | 140,000 | 150,000 |