ApsaraDB for PolarDB provides Compute Plans to cover the cost of fixed-specification compute nodes in pay-as-you-go clusters, which helps lower your expenses.
Notes
-
A fixed-specification compute package's purchase and unsubscription only affect billing and do not affect the normal operation of your services.
-
A fixed-spec compute package is not region-specific. It automatically covers the fees for fixed-spec compute node resources in pay-as-you-go clusters across all regions.
-
If the remaining capacity of a fixed-spec compute package is insufficient, any excess usage is billed on a pay-as-you-go basis.
-
You cannot renew, upgrade, or downgrade fixed-spec compute packages. If a fixed-spec compute package has insufficient capacity, is about to expire, or has expired, you can purchase a new one. The capacities of multiple packages are stacked.
-
After you purchase a fixed-specification compute package, the fixed-specification resources of compute nodes in a pay-as-you-go cluster are no longer charged on an hourly basis. Instead, usage is deducted from the fixed-specification compute package on an hourly basis based on your compute consumption (CUH, or units).
Pricing
PolarDB uses CU (Capacity Unit) to measure the computing power of nodes in a cluster. The total capacity of a compute package is measured in CU*H. The CU*H consumed depends on the compute node specification. For more information, see the Consumption rules.
The unit price for a fixed-specification compute package is CNY 38 per CU*H. Discounts vary by the capacity of the compute package. For the latest pricing, refer to the buy page.
Compute package specifications
-
5 to 799 CU*H.
-
800 to 4,999 CU*H.
-
5,000 to 20,000 CU*H.
-
PolarDB provides a resource package calculator. This calculator helps you estimate the required computing power and recommends a suitable fixed-specification compute package based on your business requirements and usage duration.
-
You receive a 15% discount on packages from 800 to 4,999 CU*H and a 30% discount on packages from 5,000 to 20,000 CU*H.
Deduction rules
The computing units consumed by all nodes in a cluster are deducted hourly.
Example: Consider an Enterprise Edition cluster in the Chinese mainland with one primary node (polar.mysql.x4.large, 4 cores, 16 GB) and two read-only nodes (polar.mysql.x4.large, 4 cores, 16 GB). Each node of this specification consumes 0.04 units per hour. The cluster consumes a total of 0.12 units per hour: one primary node (1 * 0.04 units) plus two read-only nodes (2 * 0.04 units).
The polar.mysql.x4.large specification consumes 0.04 units per hour. See the consumption rule table for how many computing units different node specifications consume.
Consumption rules
-
Each value in the table represents the compute usage of a single node in a subscription compute package.
-
For more information, see How to choose between general-purpose specifications and dedicated specifications.
-
dedicated specification: Uses dedicated computing resources for more stable performance.
-
general-purpose specification: Improves cost-effectiveness by sharing idle computing resources among clusters.
-
Enterprise edition
Standard edition
Application order
If you purchase multiple fixed-specification compute packages, the fixed-specification compute packages are deducted in ascending order of their expiration time. If their expiration time is the same, the packages are deducted in the order they were purchased. The fixed-specification compute package that was purchased first is deducted first.
Best practices
-
For workloads with high or frequent fluctuations, pair a Compute Plan with the DAS autonomous service. After you purchase a Compute Plan, enable auto scaling for your pay-as-you-go cluster. When the cluster configuration is adjusted, the Compute Plan automatically applies deductions based on the new specification.
-
This example shows how to estimate Compute Plan capacity.
-
Billing plan:
pay-as-you-go + Compute Plan.
-
Sample PolarDB requirements:
-
The cluster is in a Chinese mainland region.
-
Specification A (two nodes): used for 330 days.
-
The cluster is upgraded to Specification B (two nodes) for 30 days during a sales promotion.
-
A third node of Specification B is added for the same 30-day period.
NoteIn this example, Specification A is 2 vCPUs, 8 GB and Specification B is 4 vCPUs, 16 GB.
-
-
Estimated compute consumption (units):
Estimated capacity = Hourly consumption per node × Hours × Number of nodes.
-
Specification A: 158.4 units
0.01 units × 24 hours × 330 days × 2 nodes = 158.4 units
-
Specification B: 86.4 units
0.04 units × 24 hours × 30 days × 3 nodes = 86.4 units
Note0.01 units and 0.04 units are the hourly compute consumption for Specification A and Specification B, respectively. For a list of consumption rates for all node specifications, see the Consumption Rules Table.
-
In this example, the total required capacity for the Fixed Compute Unit (FCU) is at least 244.8 CU*H (158.4 CU*H + 86.4 CU*H). To account for potential business fluctuations, we recommend adding a buffer of about 5%. Therefore, an FCU with a capacity of 260 CU*H can meet the requirements. Because the capacity of the purchased FCU is less than 800 CU*H, the price is CNY 34.2 per CU*H, and the total cost for the FCU is CNY 8,892 (260 CU*H × CNY 34.2/CU*H).
-