This topic describes the billable items and billing formulas of search indexes. Search index-based queries require extra space to store indexed data and consume read throughput.
- Billable items of indexes are independent of data tables.
- The price of each billable item of a search index is the same as that of a high-performance instance.
Billable items
Billable item | Billing method | Description | |
---|---|---|---|
Data size |
Pay-as-you-go |
Unit: GB. Billed size is rounded up to the next GB. Tablestore charges you for the total volume of indexed data on an hourly basis. The utilization of system resources varies with field types and index types. Therefore, indexed data is billed based on the volume of data compressed after you create indexes. The raw data volume in a data table does not affect this billing. |
|
Read throughput | Reserved Read Throughput |
Pay-as-you-go |
Unit: CU. Tablestore specifies a reserved read throughput based on the indexed data size. The
charges of reserved read throughput are calculated based on the following operations:
The minimum fees are based on the reserved read throughput value. For example, assume that the reserved read throughput is 10,000 CUs for an index. Each index query reads 10 rows, and the size of each row is less than 4 KB. When the number of queries per second (QPS) is less than 1,000, the actual consumed read throughput is less than the reserved read throughput, and no extra fees are charged. Calculation of reserved read throughput: The reserved read throughput is proportional to the size and number of rows of the indexed data. For example, 1 GB or 2 million rows of indexed data corresponds to a reserved read throughput of 10 CUs. When the reserved read throughput values corresponding to the data size and the number of rows are different, the system uses the larger one as the reserved read throughput. Note
|
Additional throughput |
Pay-as-you-go |
The portion of the actual consumed read throughput that exceeds the reserved read
throughput is charged as additional read throughput.
Unit: CU. |
|
Internet outbound traffic | Pay-as-you-go | Fees for Internet outbound traffic. Unit: GB. |
Billing formulas
The following table describes how to calculate the data size and read throughput of a search index.
Billable item | Formula | Description |
---|---|---|
Data size | ![]() |
The Size variable indicates the size of the compressed indexed data. |
Read throughput |
Reserved read throughput per index:
![]() Read throughput per query:
![]() |
|
Billing examples
Storage | Number of rows | Billing |
---|---|---|
8 GB | 9 million |
The portion of actual consumed read throughput that exceeds the reserved read throughput is charged as additional read throughput. The billing method of Internet outbound traffic is the same as that of the data table. |
100 GB | 300 million |
The portion of actual consumed read throughput that exceeds the reserved read throughput is charged as additional read throughput. The billing method of Internet outbound traffic is the same as that of the data table. |
30 TB | 10 billion |
The portion of actual consumed read throughput that exceeds the reserved read throughput is charged as additional read throughput. The billing method of Internet outbound traffic is the same as that of the data table. |