edit-icon download-icon

What are the requirements for reserved read/write throughput?

Last Updated: Apr 11, 2018

Reserved read/write throughput is an attribute of a table. The system pre-allocates resources in the background based on the table’s reserved read/write throughput configuration. This guarantees your throughput needs for a specified table.

When using CreateTable, you must specify the table’s reserved read/write throughput at its creation. Once a table has been created, you can use UpdateTable to update the table’s reserved read/write throughput configuration.

Table Store requires each tables’ reserved read throughput and write throughput to be greater than 0, but less than 5,000. If a table requires a reserved read throughput, or write throughput, to be greater than 5,000, you must open a ticket.

The measurement units for reserved read/write throughput are capacity units (CU). When applications perform Table Store read/write operations through the API, this consumes a corresponding amount of read and write CUs.

Table Store charges an hourly fee based on the sum of reserved read/write throughput for all tables in an instance. As a users’ reserved read/write throughput configuration can dynamically change, Table Store uses statistics about a table’s reserved read/write throughput generated at set time intervals to calculate the average reserved read/write throughput per hour. This value is then multiplied by the unit price to obtain the actual fee. The reserved read/write throughput unit price may be updated by Alibaba Cloud. For the latest billing details, see Pricing.

Thank you! We've received your feedback.