When you use the TimeSeries model, storage space is required to store time series data and time series metadata. Additionally, read and write operations on time series data and metadata consume read and write throughput. This topic describes the billable items of the TimeSeries model and provides billing examples.
Notes
Analytical storage is a storage replica built based on time series data that provides a higher compression ratio and faster analytical performance. The pricing for the storage and read operations is the same as the pricing for capacity instances.
Time series data consists of timestamps when data is generated and specific data values. The storage volume of time series data and the read and write throughput consumed by operations on this data are the major billable items of the TimeSeries model. You can select high-performance storage or capacity storage for data storage. The pricing for read and write operations is the same as the pricing for capacity instances.
Time series metadata contains the identifiers and properties of time series. The pricing for metadata storage is the same as the pricing for common data storage in high-performance instances. The pricing for throughput consumed by read or write operations on metadata is the same as the pricing for throughput consumed by operations on common data in high-performance instances.
When you access Tablestore over the Internet, you are charged for outbound traffic over the Internet. You are not charged for traffic over the internal network or inbound traffic.
Billable items
Time series data | Billable item | Billing method | Description |
Data in time series | Data storage |
| High-performance storage is supported when you select high-performance instance as the instance type. Capacity storage is supported when you select capacity instance as the instance type. Data in time series supports a higher data compression ratio than common data. |
|
| The pricing for the throughput that is consumed by read and write operations on data in time series is the same as the pricing for the throughput that is consumed by read and write operations on common data in capacity instances. The unit is CU. The number of CUs that are consumed by a read or write operation is calculated based on the amount of data in time series on which the read or write operation is performed. The number of write CUs that are consumed for a write operation on data in time series is the same as the amount of data that is written to Tablestore in KB. The number of read CUs that are consumed for a read operation on data in time series is one quarter of the amount of data that is read from Tablestore in KB. Important If the amount of data that is written to Tablestore is not an integer in KB, the amount is rounded up. If the amount of data that is read from Tablestore is not a multiple of 4 in KB, the amount is rounded up to the nearest multiple of 4. | |
Metadata of time series | Data storage |
| The pricing for the storage of metadata of time series is the same as the pricing for the storage of common data in high-performance instances. When you store metadata of time series in Tablestore, storage space is required for indexes. The size of the metadata of each time series is 4 KB for calculation. |
|
| The pricing for the throughput that is consumed by read and write operations on metadata of time series is the same as the pricing for the throughput that is consumed by read and write operations on common data in high-performance instances. The unit is CU. When you call the operation to update the metadata of time series or the operation to retrieve metadata of time series, the number of CUs that are consumed for each row on which the operation is performed is calculated. Important If the amount of data on which the operation is performed is less than 4 KB in size, the amount is rounded up to 4 KB. You are not charged when the system automatically updates metadata of time series. | |
Analytical storage | Data storage |
| The pricing for analytical storage is the same as the pricing for capacity storage. Analytical storage provides a higher compression ratio than data in time series. |
|
| The pricing for read and write operations is the same as the pricing for capacity instances. The number of CUs that are consumed is calculated based on the amount of data that is scanned when you access analytical storage by using the SQL engine. The number of read CUs that are consumed is one quarter of the amount of data that is read from Tablestore in KB. | |
Lastpoint index Important You are not charged during the process of building a Lastpoint index. | Data storage |
| High-performance storage is supported when you select high-performance instance as the instance type. Capacity storage is supported when you select capacity instance as the instance type. |
Pay-as-you-go read throughput |
| The pricing for read and write operations is the same as the pricing for high-performance instances or capacity instances based on the instance type. The unit is CU. The number of read CUs that are consumed is one quarter of the amount of data that is read from Tablestore in KB. When you query data in a Lastpoint index by using the SQL query feature or the search index feature, you are charged based on the billing rules of the corresponding feature. For more information, see Billable items of SQL query and Billable items of search index. Important If the amount of data on which the operation is performed is less than 4 KB in size, the amount is rounded up to 4 KB. |