Billing Overview
CPU elastic scale-up is billed in pay-as-you-go mode. You are charged for the additional CPU cores added to the instance beyond its original specification, based on the actual duration of the scale-up. This billing model has the following characteristics:
Pay-as-you-go postpaid: Fees are charged only for the number of cores and the duration of successful scale-ups. No additional fees are incurred when no scale-up occurs.
Billed by the minute: The minimum billing unit is one minute, and fees are settled and deducted hourly. Within a single billing cycle, any usage duration less than one minute is rounded up to one minute for billing purposes.
Linear accumulation: Fees increase linearly with the number of additional cores and the duration of the scale-up.
Note:
CPU elastic scale-up does not include additional resources such as IOPS.
Billing Formula
The cost of CPU elastic scale-up is calculated using the following formula:
Scale-up cost = (Unit price per core × Number of additional CPU cores) × Scale-up duration (minutes) / 60
The unit price per core is the price per CPU core per hour. The specific price is determined by the instance's region, node type, and the actual price displayed on the console.
Note:
The scale-up cost for a sharded cluster instance is calculated separately for each shard based on the actual number of additional cores, and then summed.
After you enable custom scale-up, the scale-up takes effect immediately and billing starts. Billing continues until you manually disable it. After you manually disable it, billing stops and the instance scales back to its original specification. The scale-back to the original specification may cause a brief impact. Perform this operation during off-peak hours.
Billing Unit Price
The unit price per core for CPU elastic scale-up is billed based on the instance's region. The price is the same for replica set instances and sharded cluster instances, as detailed in the following table. The actual price is subject to the price displayed on the console purchase page.
|
Beijing, Guangzhou, Shanghai, Nanjing, Chengdu, Chongqing | 0.0386 |
Hong Kong (China), Frankfurt, Seoul, Tokyo | 0.04029 |
Singapore, Bangkok, Silicon Valley, Virginia | 0.04571 |
Sao Paulo, Jakarta, Riyadh | 0.05429 |
Billing Examples
The unit price per core in the following example is used only to demonstrate the billing formula. The actual price is subject to the price displayed on the console purchase page. Assume that the unit price per core in the instance's region is USD 0.0386/core/hour.
Example 1 (Replica Set Instance)
The scale-up cost for a replica set instance is calculated separately for each node that participates in the scale-up (including the primary node and read-only/secondary nodes), and then summed.
For example, an instance has 3 nodes (1 primary node and 2 secondary nodes) with an original specification of 4 cores. The scale-up adds 2 additional cores. It is enabled at 10:00 and manually disabled at 17:00, resulting in a total scale-up duration of 7 hours.
Cost = 0.0386 × 2 × 3 × 420 / 60 = USD 1.6206
Example 2 (Sharded Cluster Instance)
The scale-up cost for a sharded cluster instance is calculated separately for each node that participates in the scale-up across all shards (including the primary node and read-only/secondary nodes of each shard), and then summed.
For example, an instance contains 2 shards. Each shard is scaled up by 2 additional cores. The scale-up is enabled at 10:00 and manually disabled at 12:00, resulting in a total scale-up duration of 2 hours. Fees are calculated separately for each shard and then summed. Assume each shard has 3 nodes (1 primary node and 2 secondary nodes).
The cost per shard = 0.0386 × 2 × 3 × 120 / 60 = USD 0.4632.
Total cost = 0.4632 × 2 = USD 0.9264
Documentation