AnalyticDB for MySQL Data Lakehouse Edition billing covers six categories: reserved resources, elastic resources, data storage, cache storage, backup storage, and API requests. This page explains what each billable item covers, how fees are calculated, and provides worked examples.
Billable items and billing rules
Reserved resource fee
Reserved resources are billed when you create a cluster or scale it up. Both pay-as-you-go and subscription billing methods are supported.
| Attribute | Details |
|---|---|
| Billable items | Reserved computing resources, reserved storage resources |
| Billing method | Pay-as-you-go or subscription |
| Billing unit | ACU (AnalyticDB Compute Unit). Each ACU equals approximately 1 core and 4 GB memory. |
| Formula | Reserved resource fee = Unit price per ACU × (ACUs for reserved computing resources + ACUs for reserved storage resources) × Usage duration |
Elastic resource fee
Elastic resource charges apply when your workload consumes resources beyond your reserved allocation. Three sub-types are billed separately.
ACU elastic resources
ACU elastic charges are triggered in two ways:
-
Scheduled scaling: When a scaling plan executes, you are billed for the elastic resources consumed during that period.
-
Auto scaling:
-
When an interactive resource group with the multi-cluster feature enabled runs jobs, you are billed for cluster resources consumed beyond the reserved allocation.
-
When a job resource group runs jobs, you are billed for elastic resources consumed beyond the reserved allocation.
-
| Attribute | Details |
|---|---|
| Billing method | Pay-as-you-go |
| Billing unit | ACU. Each ACU equals approximately 1 core and 4 GB memory. |
| Formula | Elastic resource fee = Unit price of ACU elastic resources × Number of ACUs × Usage duration |
| View usage | AnalyticDB for MySQL console > Resource Management > view elastic resource usage |
Spot instance resources
When you enable the spot instance feature, idle Spark executor resources in the AnalyticDB for MySQL resource pool become available at a lower price than standard ACU elastic resources.
Spot instance resources apply to on-demand scaling only. They cannot be used for scheduled scaling.
| Attribute | Details |
|---|---|
| Billing method | Pay-as-you-go |
| Billing unit | ACU. Each ACU equals approximately 1 core and 4 GB memory. |
| Formula | Spot instance resource fee = Unit price of spot instance resources × Number of ACUs × Usage duration |
Remote build data
After you enable the compaction service, you are billed for the data that the XUANWU_V2 engine builds remotely in the compaction service's dedicated resource pool.
| Attribute | Details |
|---|---|
| Billing method | Pay-as-you-go |
| Billing unit | GB |
| Formula | Remote build data fee = Unit price of remote build data × Amount of remote build data |
Data storage fee
Data storage covers the space occupied by data in your cluster. Hot and cold data are metered separately at different rates.
Data Lakehouse Edition uses a multi-replica storage architecture. The hot data storage fee is calculated by doubling the pay-as-you-go unit price. Cold data storage is not subject to this multiplier.
Hot and cold data storage
| Attribute | Details |
|---|---|
| Billable items | Hot data storage, cold data storage |
| Billing method | Pay-as-you-go |
| Billing unit | GB |
| Formula | Storage fee = Hot data storage fee + Cold data storage fee |
| Hot data storage fee = Unit price of hot data storage × Data amount × Usage duration × 2 | |
| Cold data storage fee = Unit price of cold data storage × Data amount × Usage duration | |
| View usage | AnalyticDB for MySQL console > Monitoring Information > view hot and cold data storage amounts |
ADB lake storage - Standard
After you enable the lake storage feature, you are billed for the lake storage space occupied by cluster data.
| Attribute | Details |
|---|---|
| Billing method | Pay-as-you-go |
| Billing unit | GB |
| Formula | ADB lake storage fee = Unit price of ADB managed lake storage × Data storage amount × Usage duration |
| View usage | AnalyticDB for MySQL console > Lake Storage > view lake storage data amount |
Cache storage fee
Disk cache size
Disk cache billing is triggered in two scenarios:
-
After you enable the disk cache feature, data from XUANWU_V2 engine tables stored in Object Storage Service (OSS) is cached on Enterprise SSDs (ESSDs). You are billed hourly for the cache size you specify.
-
After you enable the wide table engine feature, disk cache becomes available automatically. You can adjust the disk cache size to match your workload. You are billed hourly for the cache size you configure.
| Attribute | Details |
|---|---|
| Billing method | Pay-as-you-go |
| Billing unit | GB |
| Formula | Disk cache storage fee = Unit price of disk cache storage × Disk cache size × Usage duration |
Data lake storage query acceleration
After you enable the lake cache feature and specify a cache size, frequently accessed OSS objects are cached in that space. You are billed based on the cache size you configure.
| Attribute | Details |
|---|---|
| Billing method | Pay-as-you-go |
| Billing unit | GB |
| Formula | Lake cache storage fee = Unit price of lake cache storage × Lake cache size × Usage duration |
Backup storage fee
Data backup is automatically enabled when you create a cluster. The most recent backup set is retained free of charge. If a cluster has multiple backup sets, you are billed for all backup sets except the most recent one.
| Attribute | Details |
|---|---|
| Billing method | Pay-as-you-go |
| Billing unit | GB |
| Formula | Data backup storage fee = Unit price of data backup storage × (Total backup set size − Free backup set size) × Usage duration |
| View usage | AnalyticDB for MySQL console > Backup and Restoration > view total and free backup set sizes |
Request fee
Request fees apply when you enable the lake storage feature. PUT and GET requests to the OSS API are billed separately per hour.
| Billable item | Formula |
|---|---|
| ADB lake storage - PUT requests (Standard) | Unit price of PUT requests × Number of requests (per 10,000) |
| ADB lake storage - GET requests (Standard) | Unit price of GET requests × Number of requests (per 10,000) |
Billing examples
Example 1: Subscription cluster in China (Hangzhou)
Configuration: 32 ACUs of reserved computing resources + 24 ACUs of reserved storage resources, 3-month subscription.
| Billable item | Fee |
|---|---|
| Reserved computing resources | USD 21.54/ACU-month × 32 ACUs × 3 months = USD 2,067.84 |
| Reserved storage resources | USD 21.54/ACU-month × 24 ACUs × 3 months = USD 1,550.88 |
| Total (3 months) | USD 3,618.72 |
Example 2: Pay-as-you-go cluster in China (Hangzhou)
Configuration:
-
Reserved resources: 32 ACUs computing + 24 ACUs storage
-
Elastic resources: a job resource group with 0 reserved ACUs runs a Spark job of 2 cores and 4 GB memory (= 2 × 0.8 ACUs) for 1 hour
-
Data storage: 100 GB hot data + 260 GB cold data
| Category | Billable item | Fee |
|---|---|---|
| Reserved resources | Reserved computing resources | USD 0.04615/ACU-hour × 32 ACUs × 1 hour = USD 1.4768 |
| Reserved storage resources | USD 0.04615/ACU-hour × 24 ACUs × 1 hour = USD 1.1076 | |
| Elastic resources | ACU elastic resources | USD 0.04615/ACU-hour × 2 × 0.8 ACUs × 1 hour = USD 0.07384 |
| Data storage | Hot data storage | USD 0.00022/GB-hour × 100 GB × 1 hour × 2 = USD 0.044 |
| Cold data storage | USD 0.000028/GB-hour × 260 GB × 1 hour = USD 0.00728 | |
| Total per hour | USD 2.70952 |