AnalyticDB:Billable items of Enterprise Edition and Basic Edition

Billing scenario:

• You are billed for reserved resources when you create a cluster.

• Scaling out modifies the reserved resources.

Billing unit:

The resources are bundled into units and sold as ACUs. Each ACU of reserved resources is approximately equal to 1 core and 8 GB memory.

Fee calculation:

Reserved resource fee = Unit price per ACU × Single-node specifications of reserved resources × Number of reserved resource nodes × Usage duration

Billing scenario:

• Scheduled scaling: When you use a scaling plan to scale resources, you are billed for the consumed elastic resources after the scaling is executed.

• Auto scaling:

  • When you use an interactive resource group that has the multi-cluster feature enabled to run jobs, you are billed for the compute cluster resources consumed in addition to reserved resources.

  • When you use a job resource group to run jobs, you are billed for the elastic resources consumed in addition to reserved resources.

Billing unit:

The resources are bundled into units and sold as ACUs. Each ACU of elastic resources is approximately equal to 1 core and 4 GB memory.

Fee calculation:

Elastic resource fee = Unit price of ACU elastic resources × Amount of used ACU elastic resources × Usage duration

Querying usage:

You can view elastic resource usage on the Resource Management page of the AnalyticDB for MySQL console. For more information, see View monitoring information about resource groups.

Billing scope:

After you enable the spot instance feature for a job resource group, Spark jobs that use the resource group will use idle Spark Executor resources in the AnalyticDB for MySQL resource pool. The price of spot instance resources is lower than the price of ACU elastic resources.

Billing unit:

The resources are bundled into units and sold as ACUs. Each ACU of elastic resources 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

Query Usage:

You can go to the Resource Management page in the AnalyticDB for MySQL console to view spot instance resource usage. For more information, see View the computing resource usage of resource groups.

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:

Remote BUILD data fee = Unit price of remote BUILD data × Amount of remote BUILD data

Billing scenario:

Enable AI nodes when you create a cluster.

Fee calculation:

AI node fee = Unit price of AI node specifications × Number of nodes × Usage duration

Billing scope:

The space consumed by data stored during cluster operation.

Billing unit:

The billing unit is GB.

Fee calculation:

Data storage fee = Hot data storage fee + Cold data storage fee

• Enterprise Edition Hot Data Storage Fee = Unit price of hot data storage × Hot data storage volume × Usage duration × 2

  Note

  Enterprise Edition uses a multi-replica storage architecture. Therefore, the total hot data storage fee is multiplied by 2.

• Basic Edition Hot Data Storage Fee = Unit price of hot data storage × Hot data storage volume × Usage duration

• Cold data storage fee = Unit price of cold data storage × Data volume × Usage duration

Querying usage:

You can view the amount of cold data and hot data on the Monitoring & Alerting page of the AnalyticDB for MySQL console. For more information, see View monitoring information of AnalyticDB for MySQL.

Billing scope:

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

Billing unit:

The billing unit is GB.

Fee calculation:

ADB lake storage fee = Unit price of ADB lake storage × Data storage amount × Usage duration

Query usage:

You can view the amount of lake storage data in the Lake Storage page of the AnalyticDB for MySQL console.

Billing scope:

After you enable the disk cache feature, cloud disks are used to cache the data of XUANWU_V2 engine tables from OSS to ESSD cloud disks. You are billed for the disk cache size that you specify when you enable the disk cache feature.

Billing unit:

The billing unit is GB.

Fee calculation:

Disk cache fee = Unit price of disk cache × Disk cache size × Usage duration

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 for 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

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

Query usage:

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 View backup sets.

Billing scenarios:

After you enable the data lake storage feature, you are billed for the number of PUT API requests to OSS per hour.

Billing unit:

The billing unit is 10,000 requests.

Fee calculation:

AnalyticDB data lake storage - PUT request fee = Unit price of AnalyticDB data lake storage - PUT requests × Number of requests

Billing scope:

After you enable lake storage, you are billed for the number of GET API requests to OSS per hour.

Billing unit:

The billing unit is 10,000 requests.

Fee calculation:

AnalyticDB lake storage GET request fee = Unit price of AnalyticDB lake storage GET requests × Number of requests