Global table metering and billing-Tablestore(Tablestore)-阿里云帮助中心

Notes

In Capacity Unit (CU) mode, if a data table and its indexes are configured with reserved read throughput, only the read throughput that exceeds the reserved amount is billed on a pay-as-you-go basis.

Billing details

Global tables incur fees for data storage, data reads, data writes, and cross-region replication traffic.

Note

The billing method for data storage and read/write operations on each replica table is the same as that of a standard data table. For more information, see Billing overview.

The following fees apply:

Data storage fee: Each replica table stores data independently. You are billed separately for the actual amount of data stored in each table's region.
Data read fee: Covers local read operations on all replica tables.
Data write fee: Write operations can be performed only on writable replicas. Write fees are incurred only on the table to which data is directly written. Replica tables that synchronize data through asynchronous replication do not incur write fees.
Cross-region replication traffic fee: Charged for the cross-region data transfer traffic generated when data is asynchronously replicated to each replica table.

Important
The cross-region replication traffic fee for each replica is calculated separately. The fee is charged to the instance from which the data is pulled.

Billable items

VCU mode

Billable item	Billing method	Description
Storage data size	Pay-as-you-go Resource plan	The total data storage size of all replica tables. The calculation rule is the same as for a standard data table. The unit is GB.
Compute capacity	Subscription Pay-as-you-go (After you enable elastic capacity, the elastic part is billed on a pay-as-you-go basis)	All computing resources are defined by Virtual Compute Units (VCUs). One VCU is equivalent to the processing power of 4 cores and 16 GB of memory. Operations such as reading data from replica tables and writing data to tables consume VCU computing resources.
Cross-region replication traffic	Pay-as-you-go	Cross-region data transfer traffic is generated when data is asynchronously replicated to replica tables. You are billed for the actual amount of data synchronized. The unit is GB. Important During cross-region replication, data transfer is supported between instances in VCU mode and CU mode. Data transfer is also supported between storage-optimized instances and compute-optimized instances in CU mode. The fees for these transfers are cross-region replication traffic fees and do not consume computing resources.

CU mode

Billable item	Billing method	Description
Storage data size	Pay-as-you-go Resource plans	The total data storage size of all replica tables. The calculation rule is the same as for a standard data table. The unit is GB.
Read throughput	Pay-as-you-go Resource plan	The read throughput consumed by read operations on each replica table through the read API. The calculation rule is the same as for a standard data table. The unit is Capacity Unit (CU).
Write throughput	Pay-as-you-go Resource Plan	The write throughput consumed by write operations on the table through the write API. The calculation rule is the same as for a standard data table. The unit is CU.
Cross-region replication traffic	Pay-as-you-go	Cross-region data transfer traffic is generated when data is asynchronously replicated to replica tables. You are billed for the actual amount of data synchronized. The unit is GB. Important During cross-region replication, data transfer is supported between instances in VCU mode and CU mode. Data transfer is also supported in CU mode between storage-optimized instances and compute-optimized instances. The fees for these transfers are cross-region replication traffic fees and do not consume computing resources.