Pricing for different instance types
Time Series Database (TSDB) instance prices are calculated based on instance specifications and storage space. The formula is described as follows:Total instance price = Price of the instance specification + Price of storage space
TSDB instances support subscription and pay-as-you-go billing methods. If you plan to use TSDB instances for a long time, we recommend that you use the subscription billing method. Compared with the pay-as-you-go billing method, the subscription billing method allows you to reduce costs by up to 60%.
Instance specifications
An instance specification is determined based on the following two elements: write TPS and the maximum number of connected data collection points. Data collection points are the items based on which data is collected and sent to TSDB. Two examples of data collection points are the CPU usage of a server and temperature that is collected from a temperature sensor. One timeline of data is produced for each data collection point. Write TPS indicates the maximum write rate that is supported by TSDB. The write TPS is measured by the maximum number of data points that can be written per second.
Storage space
You can store raw data that is generated by your devices for subsequent processing or analysis. We recommend that you purchase storage space based on your actual data volume. Your data volume may increase over time. If the storage space cannot meet your business needs, you can clear some data or purchase additional storage space.
Subscription
Instance specification (USD/month)
Edition | Basic Edition I | Basic Edition II | Basic Edition III | Standard Edition I | Standard Edition II | Flagship Edition I | Flagship Edition II |
Specification code | tsdb.1x.basic | tsdb.3x.basic | tsdb.4x.basic | tsdb.12x.standard | tsdb.24x.standard | tsdb.48x.large | tsdb.96x.large |
Maximum data collection points | 2.4 million | 4.8 million | 10 million | 20 million | 40 million | No upper limit | No upper limit |
Write TPS (Data points/s) | 10,000 | 30,000 | 40,000 | 120,000 | 240,000 | 480,000 | 960,000 |
Chinese Mainland | 120.60 | 210.15 | 523.59 | 1045.98 | 1962.99 | 3691.05 | 7144.18 |
China (Hong Kong) | 155.68 | 277.32 | 554.63 | 1348.51 | 2798.66 | 5226.57 | 10082.24 |
Japan (Tokyo) | 174.78 | 301.35 | 602.54 | 1488.36 | 2993.44 | 5615.98 | 10861.20 |
India (Mumbai) | 134.93 | 239.86 | 479.71 | 1144.63 | 2385.83 | 4452.39 | 8585.53 |
Singapore | 160.00 | 282.69 | 565.38 | 1348.51 | 2798.66 | 5226.57 | 10082.24 |
Australia (Sydney) | 164.63 | 294.03 | 588.06 | 1437.92 | 2983.89 | 5573.74 | 10753.14 |
Malaysia (Kuala Lumpur) | 151.35 | 271.80 | 543.44 | 1303.89 | 2734.03 | 5098.21 | 9826.57 |
Indonesia (Jakarta) | 158.96 | 285.68 | 571.20 | 1381.65 | 2891.05 | 5392.69 | 10396.12 |
Germany (Frankfurt) | 150.75 | 271.20 | 542.39 | 1348.51 | 2798.66 | 5226.57 | 10082.24 |
UK (London) | 141.20 | 244.33 | 488.51 | 1227.77 | 2462.24 | 4621.65 | 8940.30 |
UAE (Dubai) | 174.18 | 321.95 | 643.89 | 1700.45 | 3528.81 | 6590.60 | 12714.18 |
US (Virginia) | 128.96 | 227.47 | 454.93 | 1080.75 | 2239.86 | 4183.59 | 8071.35 |
US (Silicon Valley) | 169.71 | 301.35 | 602.69 | 1454.48 | 3019.26 | 5639.56 | 10880.00 |
Storage space (USD/month/GB)
Chinese Mainland | China (Hong Kong) | Japan (Tokyo) | India (Mumbai) | Singapore | Australia (Sydney) | Malaysia (Kuala Lumpur) | Indonesia (Jakarta) | Germany (Frankfurt) | UK (London) | UAE (Dubai) | US(Virginia) | US(Silicon Valley) |
0.1045 | 0.1045 | 0.1075 | 0.1015 | 0.1045 | 0.1105 | 0.1015 | 0.1045 | 0.1045 | 0.1015 | 0.1254 | 0.1045 | 0.1045 |
Pay-as-you-go
Instance specification (USD/hour)
Edition | Basic Edition I | Basic Edition II | Basic Edition III | Standard Edition I | Standard Edition II | Flagship Edition I | Flagship Edition II |
Specification code | tsdb.1x.basic | tsdb.3x.basic | tsdb.4x.basic | tsdb.12x.standard | tsdb.24x.standard | tsdb.48x.large | tsdb.96x.large |
Maximum data collection points | 2.4 million | 4.8 million | 10 million | 20 million | 40 million | No upper limit | No upper limit |
Write TPS (Data points/s) | 10,000 | 30,000 | 40,000 | 120,000 | 240,000 | 480,000 | 960,000 |
Chinese Mainland | 0.3612 | 0.7239 | 1.4523 | 3.5821 | 5.9702 | 11.1941 | 21.7911 |
China (Hong Kong) | 0.3165 | 0.5568 | 0.8777 | 2.6806 | 5.5135 | 10.3075 | 19.8956 |
Japan (Tokyo) | 0.3314 | 0.5747 | 0.8956 | 2.8583 | 5.7687 | 10.8165 | 20.9135 |
India (Mumbai) | 0.2806 | 0.4941 | 0.7821 | 2.3702 | 4.9045 | 9.1627 | 17.6777 |
Singapore | 0.3269 | 0.5747 | 0.9075 | 2.7747 | 5.7180 | 10.6911 | 20.6389 |
Australia (Sydney) | 0.3448 | 0.6195 | 0.9941 | 3.1344 | 6.4508 | 12.0598 | 23.2792 |
Malaysia (Kuala Lumpur) | 0.3135 | 0.5568 | 0.8896 | 2.6821 | 5.5866 | 10.4284 | 20.1120 |
Indonesia (Jakarta) | 0.3344 | 0.5986 | 0.9612 | 2.8971 | 6.0583 | 11.2986 | 21.7806 |
Germany (Frankfurt) | 0.3045 | 0.5433 | 0.8702 | 2.7284 | 5.6224 | 10.5165 | 20.3015 |
UK (London) | 0.2926 | 0.5075 | 0.7911 | 2.5299 | 5.0911 | 9.5493 | 18.4672 |
UAE (Dubai) | 0.3642 | 0.6732 | 1.1090 | 3.4463 | 7.2254 | 13.4747 | 25.9717 |
US (Virginia) | 0.2836 | 0.4986 | 0.7851 | 2.3941 | 4.9314 | 9.2209 | 17.8000 |
US (Silicon Valley) | 0.3448 | 0.6105 | 0.9687 | 2.9926 | 6.1717 | 11.5418 | 22.2806 |
Storage space (USD/hour/GB)
Chinese Mainland | China (Hong Kong) | Japan (Tokyo) | India (Mumbai) | Singapore | Australia (Sydney) | Malaysia (Kuala Lumpur) | Indonesia (Jakarta) | Germany (Frankfurt) | UK (London) | UAE (Dubai) | US(Virginia) | US(Silicon Valley) |
0.000147 | 0.000150 | 0.000150 | 0.000150 | 0.000150 | 0.000180 | 0.000150 | 0.000150 | 0.000150 | 0.000150 | 0.000180 | 0.000150 | 0.000150 |
Example
For example, you have 10,000 devices and each device has 16 data collection points. Data is reported every 20 seconds from each data collection point. You can calculate the write TPS and the number of timelines based on the following formulas:Number of timelines = Number of data collection points = 10,000 × 16 = 160,000Write TPS = 160,000 × (1/20) = 8,000 data points/sIn this case, we recommend that you purchase Basic Edition I, and purchase storage space based on your actual data volume.