AnalyticDB for MySQL:Billable items of Data Warehouse Edition (V3.0)

Billing scope:

You are billed for elastic I/O resources when you purchase elastic I/O resources or change their specifications when you scale up a cluster. For more information about the billing rules for scale-up, see Billing of configuration changes.

Limits:

Elastic I/O resources can be purchased only for elastic clusters that have a minimum of 32 cores and 128 GB memory.

Recommendations:

When purchasing elastic I/O resources, we recommend that you purchase enough elastic I/O units (EIUs) to have at least half the number of basic computing resource cores in your cluster.

Fee calculation:

Elastic I/O resource fee = Unit price per EIU × Number of EIUs × Usage duration

Billing scope:

You are billed for elastic computing resources when resource scaling is performed based on the scaling plans that you create.

The scaling plans must be of the Default Proportional Scaling for Computing Resources and EIUs type.

Limits:

Support for resource scaling may be limited by the minor version and specifications of your cluster. For more information, see Create a resource scaling plan.

Fee calculation:

Elastic computing resource fee = Unit price of elastic computing resources per compute node × Number of compute nodes × Usage duration

Billing scope:

You are billed for storage resources based on the actual storage space occupied.

You can purchase storage for both subscription and pay-as-you-go clusters. The unit price of storage for subscription clusters is different from that for pay-as-you-go clusters.

Fee calculation:

Storage fee = Hot data storage fee + Cold data storage fee

• Hot data storage fee = Unit price of hot data storage × Data volume × Usage duration

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

Viewing storage 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.