Billable items of the TimeSeries model-Tablestore(Tablestore)-阿里云帮助中心

Usage notes

data in a time series. high compression ratio
Data in time series consists of points in time at which data is generated and specific data values. The storage volume of data in time series and the read and write throughput that are consumed by the read and write operations on data in time series are the major billable items of the TimeSeries model. You can select high-performance storage or capacity storage based on the instance type that you specified. 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.
Metadata of time series contains the identifiers and properties of time series. 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. The pricing for the throughput that is consumed by a read or write operation on metadata of time series is the same as the pricing for the throughput that is consumed by a read or write operation 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 and inbound traffic.

Billable items

Time series data	Billable item	Billing method	Description
Data in time series	Data storage	Pay-as-you-go Resource plan	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.
Data in time series	Metered write throughput Metered read throughput	Pay-as-you-go Resource plan	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. Unit: 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	Pay-as-you-go Resource plan	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.
Metadata of time series	Metered write throughput Metered read throughput	Pay-as-you-go Resource plan	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. Unit: 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 Store	Data storage	Pay-as-you-go Resource plan	The pricing for the storage of metadata of time series is the same as the pricing for the storage of common data in capacity instances. Analytical Store provides higher compression ratio than data in time series.
Analytical Store	Metered write throughput Metered read throughput	Pay-as-you-go Resource plan	The pricing for the throughput that is consumed by read and write operations on data of Analytical Store is the same as the pricing for the throughput that is consumed by read and write operations on common data in capacity instances. The number of CUs that are consumed by a read or write operation is calculated based on the the amount of Analytical Store data scanned by an SQL engine. The number of read CUs that are consumed for a read operation on data in Lastpoint indexs is one quarter of the amount of data that is read from Tablestore in KB.
Lastpoint index Important You are not charged for building a Lastpoint index.	Data storage	Pay-as-you-go Resource plan	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.
	Metered read throughput	Pay-as-you-go Resource plan	The pricing for the throughput that is consumed by read and write operations on data in Lastpoint indexs is the same as the pricing for the throughput that is consumed by read and write operations on common data in capacity instances or high-performance instances. Unit: CU. The number of read CUs that are consumed for a read operation on data in Lastpoint indexs is one quarter of the amount of data that is read from Tablestore in KB. If you use the SQL query or search index feature to query data in Lastpoint indexes, you are charged based on the billing rules of the features. For more information, see Billable items of SQL query and Billable items of search indexes. 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.

Billing Examples

The following table lists，cost calculation examples when using the time series model。

Example Scenario

Cost Calculation

110,000 devices，Each device corresponds to one time series
Each device transmits10 KBdata
Daily1000query operations：After searching devices,，scan20 MBdata
Total existing data size1 TB
Time series data uses capacity storage，time series metadata uses high-performance storage

This scenario details the cost calculation for each billing item。

Time Series Data Billing

Data Storage

Storage capacity is1 TB，capacity storage unit price is0.3yuan/GB//month。

Monthly cost：1 TB*0.3yuan/GB/month*1month=300yuan
Data write

The unit price for capacity-based pay-as-you-go write throughput is 0.002yuan/10,000CU。

Write throughput per device per operation：10 KB/1 KB=10 CU

Monthly cost：10 CU*1month/1minute*0.002yuan/10,000CU=864yuan
Data read

The unit price for capacity-based pay-as-you-go read throughput is 0.004yuan/10,000CU。

Read throughput per device per operation：20 MB/4 KB=5000 CU

Monthly cost：5000 CU*1000times/day*30days*0.004yuan/10,000CU=61yuan

Timeline metadata billing

Metadata storage

The unit price for high-performance storage is1.08yuan/GB/month。

Storage capacity：110,000*4 KB=39 MB

Monthly fee：39 MB*1month*1.08yuan/GB/month=0.04yuan
Metadata queries

The unit price for high-performance pay-as-you-go read throughput is0.01yuan/10,000CU。

Single pay-as-you-go read throughput：4 KB/4 KB=1 CU

Monthly fee：1 CU*1000times/day*30days*0.01yuan/10,000CU=0.03yuan

110,000 devices，Each device corresponds to one timeline
Daily data writes137 GB
Daily data scans19 GB
Total size of existing data1 TB
Timeline data uses capacity storage，timeline metadata uses high-performance storage

This scenario is used to quickly estimate required costs，where data write costs are calculated at0.21yuan/GB//day estimate，data read costs are calculated at0.1yuan/GB//day estimate。

Timeline Data Billing

Data Storage

Storage volume is1 TB，capacity storage unit price is0.3yuan/GB//month。

Monthly cost：1 TB*0.3yuan/GB//month*1month=300yuan
Data writes

Fees are calculated at0.21yuan/GB//day estimated。

Monthly fee：137GB*0.21yuan/GB//day*30days=863yuan
Data reads

Fees are calculated at0.1yuan/GB//day estimated。

Monthly fee：19 GB*0.1yuan/GB//day*30days=57yuan

Timeline metadata billing

The fee proportion is small，and is not shown here，The actual fees shall prevail。