AnalyticDB:Billable items of Enterprise Edition and Basic Edition

Compute fees

Reserved resources

Billed when you create a cluster or scale out. Reserved resources are the baseline compute capacity committed to your cluster.

• Billing method: Pay-as-you-go or Subscription

• Billing unit: ACU (Alibaba Cloud Unit) — 1 ACU ≈ 1 core and 8 GB of memory

• Formula: Unit price per ACU × Single-node specs × Number of nodes × Usage duration

ACU-hour plans can offset the cost of reserved resources for pay-as-you-go clusters. For details, see ACU-hour plans.

ACU elastic resources

Billed when elastic resources are consumed beyond your reserved capacity. Two scenarios trigger this charge:

• Scheduled scaling: Resources consumed after a scaling plan executes.

• Auto scaling:

  • Interactive resource groups with multi-cluster enabled — you are billed for compute resources that exceed the reserved capacity.

  • Job resource groups — billed for elastic resources beyond reserved capacity.

• PromQL resource group: After you create a PromQL resource group, the combined ACU count across all four node types — storage, write, query, and auth — is billed at the ACU elastic resource rate based on usage duration. Billing starts when the resource group enters the Running state and stops when it is released.

Billing details:

• Billing method: Pay-as-you-go

• Billing unit: ACU — 1 ACU ≈ 1 core and 4 GB of memory

• Formula: Unit price of ACU elastic resources × Amount used × Usage duration

• View usage: Resource Management page in the AnalyticDB for MySQL console. See View monitoring information about resource groups.

Only ACU-hour plans can offset ACU elastic resource costs. For details, see ACU-hour plans.

Spot instance resources

When you enable the spot instance feature for a job resource group, Spark jobs in that group use idle Spark Executor resources from the AnalyticDB for MySQL resource pool. Spot instance pricing is lower than ACU elastic resource pricing.

• Billing method: Pay-as-you-go

• Billing unit: ACU — 1 ACU ≈ 1 core and 4 GB of memory

• Formula: Unit price of spot instance resources × Number of ACUs × Usage duration

• View usage: Resource Management page in the AnalyticDB for MySQL console. See View the computing resource usage of resource groups.

Remote build data

When you enable the compaction service, the XUANWU_V2 engine builds data remotely in the compaction service's dedicated resource pool. You are billed for the volume of data built remotely.

• Billing method: Pay-as-you-go

• Billing unit: GB

• Formula: Unit price of remote BUILD data × Amount of remote BUILD data

AI node fees

AI nodes are enabled at cluster creation time and billed by subscription.

• Billing method: Subscription

• Formula: Unit price of AI node specifications × Number of nodes × Usage duration

Storage fees

Hot data storage and cold data storage

• You are billed for the storage space your cluster data occupies.

• PromQL resource group: After you create a PromQL resource group, storage node data disks are billed at the hot data storage rate. The billable amount is the allocated quota (disk size per node × number of storage nodes), regardless of how much data is actually written.

• Billing method: Pay-as-you-go

• Billing unit: GB

• Formula: Data storage fee = Hot data storage fee + Cold data storage fee

  • Enterprise Edition: Unit price × Hot data volume × Usage duration × 2 Enterprise Edition uses a multi-replica storage architecture, so the hot data storage fee is multiplied by 2.

  • Basic Edition: Unit price × Hot data volume × Usage duration

  • Cold data storage: Unit price × Data volume × Usage duration

• View usage: Monitoring & Alerting page in the AnalyticDB for MySQL console. See View monitoring information of AnalyticDB for MySQL.

Storage plans can offset storage costs. For details, see Storage Plans.

ADB lake storage - Standard

When you enable the lake storage feature, you are billed for the lake storage space occupied by cluster data.

• Billing method: Pay-as-you-go

• Billing unit: GB

• Formula: Unit price of ADB lake storage × Data storage amount × Usage duration

• View usage: Lake Storage page in the AnalyticDB for MySQL console. See View the amount of lake storage data.

Cache storage fees

Disk cache

• When you enable the disk cache feature, data from XUANWU_V2 engine tables stored in OSS is cached on ESSD cloud disks. You are billed for the disk cache size you specify.

• PromQL resource group: After you create a PromQL resource group, query node cache disks are billed at the disk cache rate. The billable amount is the allocated cache quota (cache disk size per node × number of query nodes), regardless of actual usage.

• Billing method: Pay-as-you-go

• Billing unit: GB

• Formula: Unit price of disk cache × Disk cache size × Usage duration

Lake storage query acceleration

When you enable the lake cache feature and specify a cache size, frequently accessed OSS objects are cached in that space. You are billed for the cache size you specify when enabling the feature.

• Billing method: Pay-as-you-go

• Billing unit: GB

• Formula: Unit price of lake cache storage × Lake cache size × Usage duration

Backup storage fee

Data backup storage

The data backup feature is automatically enabled when you create a cluster.

The most recent backup set is always free. You are only charged for additional backup sets beyond the most recent one.

• Billing method: Pay-as-you-go

• Billing unit: GB

• Formula: Unit price of data backup storage × (Total backup set size - Free backup set size) × Usage duration

• View usage: Backup and Restoration page in the AnalyticDB for MySQL console. See View backup sets.

Request count fees

ADB lake storage - PUT request (Standard)

When you enable the data lake storage feature, you are billed per hour for PUT API requests sent to OSS.

• Billing method: Pay-as-you-go

• Billing unit: 10,000 requests

• Formula: Unit price of PUT requests × Number of requests

ADB lake storage - GET request (Standard)

When you enable the lake storage feature, you are billed per hour for GET API requests sent to OSS.

• Billing method: Pay-as-you-go

• Billing unit: 10,000 requests

• Formula: Unit price of GET requests × Number of requests