This topic describes the billable items and billing rules of AnalyticDB for MySQL Data Lakehouse Edition clusters.
Bill composition
The following figure shows the bill composition of AnalyticDB for MySQL Data Lakehouse Edition clusters.
Billable items and billing rules
The following table describes how the fees for each billable item are calculated.
Category | Billable item | Billing method | Description |
Reserved resource fee |
| Pay-as-you-go Subscription Note ACU-hour plans can be used to offset the reserved resources of pay-as-you-go clusters. For more information, see ACU-hour plans. | Billing scope:
Billing unit: The resources are bundled into units and sold as AnalyticDB compute units (ACUs). Each ACU is approximately equal to 1 core and 4 GB memory. Fee calculation: Reserved resource fee = Unit price per ACU × (Number of ACUs for reserved computing resources + Number of ACUs for reserved storage resources) × Usage duration |
Elastic resource fee | ACU elastic resources | Pay-as-you-go Note Only ACU-hour plans can be used to offset ACU elastic resources. For more information, see ACU-hour plans. | Billing scope:
Billing unit: The resources are bundled into units and sold as ACUs. Each ACU is approximately equal to 1 core and 4 GB memory. Fee calculation: Elastic resource fee = Unit price of ACU elastic resources × Number of ACUs × Usage duration Viewing information: You can log on to the AnalyticDB for MySQL console and go to the Resource Management page to view the amount of used elastic resources. For more information, see View monitoring information about resource groups. |
Spot instance resources | Pay-as-you-go Note The reserved computing resources that are not allocated to resource groups can be used to offset spot instance resources. | Billing scope: After you enable the spot instance feature, you are billed for the idle Spark executor resources that are used by Spark jobs in the AnalyticDB for MySQL resource pool. The price of spot instance resources is lower than the price of ACU elastic resources. Important Spot instance resources can be used for auto scaling scenarios, but not scheduled scaling scenarios. Billing unit: The resources are bundled into units and sold as ACUs. Each ACU is approximately equal to 1 core and 4 GB memory. Fee calculation: Spot instance resource fee = Unit price of spot instance resources × Number of ACUs × Usage duration Viewing information: You can log on to the AnalyticDB for MySQL console and go to the Resource Management page to view the amount of used spot instance resources. For more information, see the "View the information about computing resources of a resource group" section of the View monitoring information about resource groups topic. | |
Remotely built data | Pay-as-you-go | Billing scope: After you enable the compaction service, you are billed for the data that is remotely built by the XUANWU_V2 engine in the independent resource pool of the compaction service. Billing unit: The billing unit is GB. Fee calculation: Remotely built data fee = Unit price of remotely built data × Amount of remotely built data | |
Data storage fee |
| Pay-as-you-go Note Storage plans can be used to offset the costs of storage. For more information, see Storage plans. | Billing scope: You are billed for data storage based on the actual storage usage. Fee calculation: Data storage fee = Hot data storage fee + Cold data storage fee
Viewing information: You can log on to the AnalyticDB for MySQL console and go to the Monitoring Information page to view the amount of storage used for hot data and cold data. For more information, see View monitoring information of AnalyticDB for MySQL. |
Cache storage fee | Disk cache storage | Pay-as-you-go | Billing scope:
Billing unit: The billing unit is GB. Fee calculation: Disk cache storage fee = Unit price of disk cache storage × Disk cache size × Usage duration |
Lake cache storage | Pay-as-you-go | Billing scope: After you enable the lake cache feature and specify the cache size, OSS objects that are frequently accessed are cached in the cache space. You are billed based on the cache size that you specify when you enable the lake cache feature. Billing unit: The billing unit is GB. Fee calculation: Lake cache storage fee = Unit price of lake cache storage × Lake cache size × Usage duration | |
Backup storage fee | Data backup storage | Pay-as-you-go | Billing scope: After you create an AnalyticDB for MySQL cluster, the data backup feature is automatically enabled for the cluster. The most recent data backup set of the cluster is retained free of charge. If a cluster contains multiple data backup sets, you are charged for the data backup sets other than the most recent one based on the pay-as-you-go billing method. Billing unit: The billing unit is GB. Fee calculation: Data backup storage fee = Unit price of data backup storage × (Total backup set size - Free backup set size) × Usage duration Viewing information: You can log on to the AnalyticDB for MySQL console and go to the Backup and Restoration page to view the total backup set size and the free backup set size. For more information, see the "View backup sets" section of the Manage backups topic. |
Billing examples
The following billing examples are provided for reference only. See the service console or buy page to obtain the actual prices of individual resources.
Example 1
You purchase a subscription Data Lakehouse Edition cluster in the China (Hangzhou) region. The cluster has 32 ACUs of reserved computing resources and 24 ACUs of reserved storage resources. The subscription period is three months.
The following table describes the fees for individual resources.
Category | Billable item | Fee |
Reserved resources | Reserved computing resources | USD 21.54 per ACU-month × 32 ACUs × 3 months = USD 2,067.84 |
Reserved storage resources | USD 21.54 per ACU-month × 24 ACUs × 3 months = USD 1,550.88 |
Total fees for three months = USD 2,067.84 + USD 1,550.88 = USD 3,618.72
Example 2
You purchase a pay-as-you-go Data Lakehouse Edition cluster in the China (Hangzhou) region.
Reserved resources: The cluster has 32 ACUs of reserved computing resources and 24 ACUs of reserved storage resources.
Elastic resources: A job resource group that has 0 ACUs of reserved resources is created. The job resource group is used to run a Spark job of 2 cores and 4 GB memory (equivalent to 2 × 0.8 ACUs) for 1 hour.
Data storage: The cluster stores 100 GB of hot data and 260 GB of cold data.
The following table describes the fees for individual resources.
Category | Billable item | Fee |
Reserved resources | Reserved computing resources | USD 0.04615 per ACU-hour × 32 ACUs × 1 hour = USD 1.4768 |
Reserved storage resources | USD 0.04615 per ACU-hour × 24 ACUs × 1 hour = USD 1.1076 | |
Elastic resources | ACU elastic resources | USD 0.04615 per ACU-hour × 2 × 0.8 ACUs × 1 hour = USD 0.07384 |
Data storage | Hot data storage | USD 0.000425 per GB-hour × 100 GB × 1 hour = USD 0.0425 |
Cold data storage | USD 0.000028 per GB-hour × 260 GB × 1 hour = USD 0.00728 |
Total fees per hour = USD 1.4768 + USD 1.1076 + USD 0.07384 + USD 0.0425 + USD 0.00728 = USD 2.70802
References