Starting November 29, 2024, the maximum IOPS for ApsaraDB RDS for MySQL instances with local disks increases to 150,000 at no additional cost. The new limit applies automatically to newly purchased instances. Existing instances require a manual restart or a specification change to activate the increase.
Applicable scope
This change applies to:
-
All primary RDS for MySQL instances with local disks. For the full list of instance types, see Instance types for standard primary ApsaraDB RDS for MySQL instances (original x86 architecture).
-
All read-only RDS for MySQL instances with local disks. For the full list, see Instance types for standard read-only ApsaraDB RDS for MySQL instances (original x86 architecture).
This change does not apply to phased-out instance types. To take advantage of the higher IOPS limit, change your instances to an available instance type.
What you need to do
Newly purchased instances (on or after November 29, 2024): No action required. The increased maximum IOPS takes effect automatically.
Existing instances (purchased before November 29, 2024): The increase does not take effect automatically. To activate it, do one of the following:
-
Restart the instance — the instance is unavailable for approximately 30 seconds during the restart. Schedule the restart during off-peak hours and make sure your application can automatically reconnect after the restart.
Usage notes
Monitoring impact: After the maximum IOPS increases, your IOPS usage metric will drop. This is expected behavior. IOPS usage is calculated as:
IOPS usage = Actually used IOPS / Instance maximum IOPSBecause the denominator (maximum IOPS) increases while actual usage stays the same, the percentage decreases. No action is required.
Verify the new limit: To confirm the updated maximum IOPS for your instance, go to the ApsaraDB RDS console. On the Instances page, click the instance ID. On the Basic Information tab, find Maximum IOPS in the Configuration Information section.
Maximum IOPS before and after the adjustment
The actual maximum IOPS after the adjustment varies by instance type. The following tables list the values for each instance type.
Primary instance types
| Instance family | Instance type | CPU cores and memory | Max IOPS before | Max IOPS after |
|---|---|---|---|---|
| General-purpose | 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 | 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 | 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 | CPU cores and memory | Max IOPS before | Max IOPS after |
|---|---|---|---|---|
| General-purpose | 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 | 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 | rds.mysql.st.h43 | 60 cores, 470 GB | 120,000 | 150,000 |
| rds.mysql.st.v52 | 90 cores, 720 GB | 140,000 | 150,000 |