ApsaraDB RDS for MySQL instances that run RDS High-availability Edition with local disks and use general-purpose instance types support automatic performance scaling starting July 5, 2024.
Description
Continuous business development, data volume increase, and new service or feature release can cause the database traffic to increase and computing resources to be insufficient. If the issues occur, you can increase the computing resources of your RDS instance, such as CPU cores. Database Autonomy Service (DAS) provides the automatic performance scaling feature for your RDS instance to handle traffic spikes during peak hours. When traffic decreases, DAS automatically scales down the instance specifications to prevent resource waste.
Effective date
July 5, 2024
Billing rules
By default, the feature is disabled for RDS instances that run RDS High-availability Edition with local disks and use general-purpose instance types, and no fees are generated. If you enable the feature, you are charged based on the pay-as-you-go billing method. The following describes the unit price of the feature.
Region | Unit price (USD per CPU core-hour) |
China (Zhangjiakou) and China (Ulanqab) | 0.063 |
China (Hong Kong) and South Korea (Seoul) | 0.134 |
Japan (Tokyo) | 0.100 |
Malaysia (Kuala Lumpur) | 0.102 |
Singapore and Indonesia (Jakarta) | 0.155 |
Germany (Frankfurt) and UK (London) | 0.078 |
US (Virginia) and US (Silicon Valley) | 0.129 |
UAE (Dubai) | 0.091 |
Australia (Sydney) Closing Down | 0.106 |
Other regions | 0.083 |
For RDS instances that use local disks, the automatic performance scaling feature is billed per minute, and a bill is generated once every hour on the hour. The fee for an automatic performance scaling operation is calculated by using the following formula: Hourly fee charged per CPU core × Number of CPU cores that are added × Scaling duration measured in hours.
For example, an RDS instance resides in the China (Hangzhou) region and provides 4 CPU cores. If the RDS instance automatically scales up to 8 CPU cores and the scaling duration spans 30 minutes, you are charged USD 0.166 based on the following calculation: USD 0.083 (the unit price per CPU core-hour) × 4 (the number of CPU cores that are added) × 0.5 (the scaling duration measured in hours) = USD 0.166.
Limits
Limits on instances
Billing method: subscription or pay-as-you-go.
NoteIf the RDS instance uses the serverless billing method, the RDS instance automatically scales up. You do not need to configure automatic performance scaling.
RDS edition: RDS High-availability Edition.
Storage type: local disk.
Product type: standard.
Instance type: general-purpose instance type.
Region: The region in which the RDS instance resides supports the anomaly detection feature of DAS. For more information, see Anomaly detection.
Account: The balance in your Alibaba Cloud account is sufficient.
Limits on features
For RDS instances that use local disks, the automatic performance scaling feature can increase the number of CPU cores and the IOPS but does not increase the memory capacity or the maximum number of connections.
RDS instances that use local disks cannot automatically scale up if the hosts on which the instances are deployed cannot provide sufficient resources. The probability of a host failing to provide sufficient resources is less than 1%.
Performance scaling operations are performed only on primary RDS instances that use local disks. If a primary/secondary switchover is triggered after the primary RDS instance is scaled up, one of the following situations occurs:
If the primary RDS instance (original secondary RDS instance) meets the conditions to trigger a scale-up or a scale-down, the system performs the scaling operation on the primary RDS instance.
If the secondary RDS instance (original primary RDS instance) meets the conditions to trigger a scale-down, the system scales down the secondary RDS instance to the original specifications.