Search index-based queries require extra space to store indexed data and consume read throughput. This topic describes the billing items and billing formulas of search indexes.

Note
  • The metering and billing of indexes are independent of base tables.
  • The price of each billing item of a search index is the same as that of a high-performance instance.

Billing items

Billing 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 base 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:
  • When you create a search index, Tablestore reads data from a base table, which consumes read throughput.
  • Tokenization during the creation of a search index also consumes read throughput. Fees incurred from tokenization are included in the fees for the reserved read throughput.
  • To ensure index and query performance, some indexed data is loaded to the memory in advance and remains in memory. Such data consumes read throughput. Fees incurred from these operations are also included in the fees for the reserved read throughput.

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
  • The maximum reserved read throughput for Tablestore is 100,000 CUs.
  • When the data size is less than 200 MB and the number of rows is less than 400,000, the reserved read throughput for Tablestore must be 20 CUs, which is suitable for tests that involve a small amount of data. When the data size is greater than or equal to 200 MB or the number of rows is greater than or equal to 400,000, the reserved read throughput must be greater than or equal to 100 CUs.
Additional throughput

Pay-as-you-go

Unit: CU

The portion of the actual consumed read throughput that exceeds the reserved read throughput is charged as additional read throughput.
Internet outbound traffic Pay-as-you-go

Unit: GB

Fees for Internet outbound traffic.

Billing formulas

The following table describes how to calculate the data size and read throughput of a search index.

Billing item Formula Description
Data size fig_tablestore_en_001 The Size parameter indicates the size of a compressed index.
Read throughput
Reserved read CUs per index:reservedCU
Read CUs per query:cuperquery
  • The Size parameter indicates the size of a compressed index.
  • The Rows parameter indicates the total number of rows in an index, except for child rows in a nested query.
  • The ReturnRowSize parameter indicates the size of returned rows.
  • The ReturnRowCount parameter indicates the number of returned rows.

Billing examples

Storage Number of rows Billing
8 GB 9 million rows
  • Storage fees: 8 GB × USD 0.00030/GB/hour = USD 0.0024/hour
  • Calculation of reserved read throughput: 8 GB of data corresponds to 80 CUs and 9 million rows correspond to 45 CUs.

    Fees of reserved read throughput: 80 CUs × USD 0.0002/CU/hour = USD 0.016/hour

  • Total fees: USD 0.0024/hour + USD 0.016/hour = USD 0.0184/hour

The portion of the actual consumed read throughput that exceeds the reserved read throughput is charged as additional read throughput. The billing method of the Internet downstream traffic is the same as that of the primary table.

100 GB 300 million rows
  • Storage fees: 100 GB × USD 0.00030/GB/hour = USD 0.03/hour
  • Calculation of reserved read throughput: 100 GB of data corresponds to 1,000 CUs and 300 million rows correspond to 1,500 CUs. The reserved read throughput is 1,500 CUs.

    Fees of reserved read throughput: 1,500 CUs × USD 0.0002/CU/hour = USD 0.3/hour

  • Total fees: USD 0.03/hour + USD 0.3/hour = USD 0.33/hour

The portion of the actual consumed read throughput that exceeds the reserved read throughput is charged as additional read throughput. The billing method of the Internet downstream traffic is the same as that of the primary table.

30 TB 10 billion rows
  • Storage fees: 30,000 GB × USD 0.00030/GB/hour = USD 9/hour
  • Calculation of reserved read throughput: 30 TB of data corresponds to 300,000 CUs and 10 billion rows correspond to 50,000 CUs. Although the former CU value is larger (300,000 CUs), it exceeds the maximum reserved read throughput of 100,000 CUs. Therefore, the reserved read throughput is 100,000 CUs.

    Fees of reserved read throughput: 100,000 CUs × USD 0.0002/CU/hour = USD 20/hour

  • Total fees: USD 9/hour + USD 20/hour = USD 29/hour

The portion of the actual consumed read throughput that exceeds the reserved read throughput is charged as additional read throughput. The billing method of the Internet downstream traffic is the same as that of the primary table.

Note The price in the preceding table is for reference only. For more information, visit the Tablestore console.