Reserved read and write throughput is an attribute of data tables in high-performance instances. The unit of reserved read and write throughput is capacity unit (CU). The system reserves resources for a data table based on the reserved read and write throughput configurations of the table to meet the throughput demand on the table.
Configuration description
When you create a data table in a high-performance instance, you can specify the reserved read or write throughput for the data table based on your business requirements.
You can set the reserved read or write throughput for a data table to a value ranging from 0 to 100000.
To set the reserved read or write throughput to a value that is greater than 100000, submit a ticket.
After you create a data table, you can update the reserved read or write throughput configurations of the data table. For more information, see Update a data table.
Billing
If you set the reserved read or read throughput to a value other than 0, you are charged regardless of whether you initiate read or write requests.
Read and write CUs are consumed when you call Tablestore operations to read and write data.
Billing unit
The metering units of reserved read and write throughput are read CUs and write CUs.
Billing cycle
You are charged on an hourly basis for reserved read and write throughput of all data tables in Tablestore high-performance instances.
You can modify the reserved read and write throughput for a data table. Tablestore collects statistics for the total reserved read and write throughput of data tables at fixed intervals. Then it calculates the average reserved read and write throughput per hour, and calculates fees by multiplying the average total reserved read and write throughput per hour by the unit price.
Unit price
The unit price of reserved read and write throughput may change. For more information, see the Tablestore Pricing page.