Tablestore uses the following four dimensions to meter the resources used by applications and generate the bills: Data storage, the reserved read/write throughput, the amount of data transferred, the additional read/write throughput and the reserved read/write throughput.

The following prices are for reference only. The exact price will be based on the customized plan you choose.

Tablestore charges hourly fees based on the total volume of instance data. Due to constant changes in the total data volume, Tablestore collects statistics on the total data volume of all table partitions at regular intervals to calculate the average total data volume per hour. The average value is multiplied by the unit price to get the billing fee.

Data Storage

Tablestore charges fees when applications access the Internet downstream traffic of Tablestore. Applications’ use of the HTTP method to access the responses returned by Tablestore is the main component of the downstream traffic. Even if the operation fails, the operation failure information returned by Tablestore will still produce downstream traffic.

Tablestore only charges for the Internet downstream traffic, not for the intranet downstream traffic or the Internet upstream traffic. The access among different regions also belongs to the Internet access.

The additional throughput is the portion of the actual consumed read/write throughput that exceeds the reserved read/write throughput per second. The additional read/write throughput is measured every second.

Tablestore accumulates the additional read throughputs and write throughputs of all tables in an instance during every billing cycle. The actual consumed additional throughput is multiplied by the corresponding unit price to get the billing fee.

The Additional Read Throughput

The Additional Write Throughput

The reserved read/write throughput is a table’s attribute. You can set a proper reserved read/write throughput for your data tables to reduce the costs of resource usage.

Tablestore charges an hourly fee for the total reserved read/write throughput of all tables in an instance. The configured reserved read/write throughput may change constantly. Tablestore collects the tables’ reserved read/write throughput at regular intervals to calculate the hourly average throughput. The average value is multiplied by the unit price to get the billing fee.

The Reserved Read Throughput

The Reserved Write Throughput