Starting September 19, 2025 (Singapore Time), the default maximum number of connections and maximum IOPS have been increased for specific dedicated instance types of ApsaraDB RDS for MySQL with Premium Local SSDs.
Background information
As the evloving of ApasaDB RDS, Alibaba Cloud has increased the default maximum number of connections and maximum IOPS for specific dedicated ApsaraDB RDS for MySQL instances that use Premium Local SSDs.
The new default maximum number of connections and maximum IOPS depend on the instance type. For more information, see the details in the following section of this topic.
You do not need to pay additional fees for this adjustment.
Scope
Effective date and method
Instances that use Premium Local SSDs and are created on and after September 19, 2025 (Singapore Time): The default maximum number of connections and the maximum IOPS are automatically increased.
Instances that use Premium Local SSDs and are created before September 19, 2025 (Singapore time): The default maximum number of connections and the maximum IOPS are increased only after you manually restart the instances or change the specifications of the instances.
You can confirm whether the maximum number of connections and maximum IOPS of your instance are increased by performing the following steps: 1. Go to the RDS console and click the ID of the instance. 2. In the section of the instance details page, view the values of Maximum Connections and Maximum IOPS.
Notes
Restarting an instance causes a temporary disconnection of about 30 seconds. If you plan to restart an existing instance to increase its maximum IOPS, ensure that your application can automatically reconnect to the instance and restart the instance in a time window suitable for your business.
An increase in the maximum IOPS of an instance causes a decrease in its IOPS utilization based on the following formula:
IOPS Utilization = Actual IOPS Used / Maximum IOPS for the Instance. A sudden drop in the monitored IOPS utilization is expected.
Before and after: Default maximum number of connections
The following table compares the default maximum number of connections for dedicated RDS for MySQL instances with Premium Local SSDs before and after the increase.
Instance family | Instance type | CPU and memory | Maximum number of connections before increase | Maximum number of connections after increase |
Dedicated | mysql.x8.medium.2 | 2 cores, 16 GB | 2,500 | 8,000 |
mysql.x4.large.2 | 4 cores, 16 GB | 2,500 | 8,000 | |
mysql.x8.large.2 | 4 cores, 32 GB | 5,000 | 12,000 | |
mysql.x4.xlarge.2 | 8 cores, 32 GB | 5,000 | 12,000 | |
mysql.x8.xlarge.2 | 8 cores, 64 GB | 10,000 | 16,000 | |
mysql.x4.2xlarge.2 | 16 cores, 64 GB | 10,000 | 16,000 | |
mysql.x8.2xlarge.2 | 16 cores, 128 GB | 20,000 | 32,000 | |
mysql.x4.4xlarge.2 | 32 cores, 128 GB | 20,000 | 32,000 |
Before and after: Maximum IOPS
The following table compares the maximum IOPS for dedicated RDS for MySQL instances with Premium Local SSDs before and after the increase.
Instance family | Instance Type | CPU and Memory | Maximum IOPS before increase | Maximum IOPS after increase |
Dedicated | mysql.x8.medium.2 | 2 cores, 16 GB | 15,000 | 30,000 |
mysql.x4.large.2 | 4 cores, 16 GB | 30,000 | 40,000 | |
mysql.x8.large.2 | 4 cores, 32 GB | 40,000 | 60,000 | |
mysql.x4.xlarge.2 | 8 cores, 32 GB | 45,000 | 60,000 | |
mysql.x8.xlarge.2 | 8 cores, 64 GB | 50,000 | 90,000 | |
mysql.x4.2xlarge.2 | 16 cores, 64 GB | 60,000 | 75,000 | |
mysql.x8.2xlarge.2 | 16 cores, 128 GB | 60,000 | 105,000 | |
mysql.x4.4xlarge.2 | 32 cores, 128 GB | 80,000 | 105,000 | |
mysql.x6.4xlarge.2 | 32 cores, 192 GB | 95,000 | 120,000 | |
mysql.x8.4xlarge.2 | 32 cores, 256 GB | 100,000 | 135,000 |