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 of the table.
When you create a data table in a high-performance instance, you must specify the reserved read or write throughput. After you create the data table, you can call the UpdateTable operation to update the reserved read or write throughput of the data table.
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.
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.
You are charged for reserved read and write throughput based on the number of read and write CUs consumed. Read and write CUs are consumed when you call Tablestore API operations to read and write data in a data table.
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. The unit price of reserved read and write throughput may change. For more information, see the Tablestore Pricing page.