This topic describes the instance types of TSDB for InfluxDB®, and provides the details about the latest and previous instance types.
TSDB for InfluxDB® Basic Edition uses ultra disks, and High-availability Edition uses standard SSDs. Instance types and disk storage capacity affect the input/output operations per second (IOPS) and the throughput of a system. The performance of standard SSDs varies based on the sizes of data blocks. If the block size decreases, the throughput decreases and the IOPS increases. If the block size increases, the throughput increases and the IOPS decreases. The size of each block to be written depends on the batch size of each request. For more information, see Block Storage performance.
Unit: USD/month/GB
Japan (Tokyo) | 0.0538 | 0.6717 |
India (Mumbai) | 0.0508 | 0.5418 |
Singapore | 0.0523 | 0.5687 |
Malaysia (Kuala Lumpur) | 0.0508 | 0.5418 |
Indonesia (Jakarta) | 0.0523 | 0.5687 |
Mainland China | 0.0523 | 0.4478 |
China (Hong Kong) | 0.0523 | 0.5687 |
Germany (Frankfurt) | 0.0523 | 0.5687 |
UK (London) | 0.0508 | 0.618 |
UAE (Dubai) | 0.0672 | 0.7433 |
US (Virginia) | 0.0523 | 0.5687 |
West America (Silicon Valley) | 0.0523 | 0.515 |
Instance types and pricing
*Notes:
The performance metrics listed in the following table are estimated based on the empirical data of specific test cases. The performance metrics are for your reference only when you purchase the services. The actual system performance varies based on scenarios, system loads, data structures, and query complexity.
Benchmark reference data for write performance testing: A single write request contains 500 points, and all data is written to only one database. A total of 50,000 series is written. Each series includes 5 tag key-value pairs and 5 field key-value pairs.
Benchmark reference data for read performance testing: Each query scans 10 series and 10,000 raw points.
Performance metrics for reference
In the following table, the Number of write requests per second column lists the number of write requests per second for each edition.
In the following table, the Number of written points per second column lists the number of points that are written per second.
Query performance is measured by the number of queries per second. Each query scans 10 series and 10,000 raw points in the tests.Unit: USD/month
Series | | |
Specifications | 2 cores, 8 GB | 4 cores, 16 GB | 8 cores, 32 GB | 16 cores, 64 GB | 32 cores, 128 GB | 64 cores, 256 GB | 2 cores, 8 GB | 4 cores, 16 GB | 8 cores, 32 GB | 16 cores, 64 GB | 32 cores, 128 GB | 64 cores, 256 GB |
Write Requsets Per Second | ~50 | ~100 | ~160 | ~300 | ~500 | ~800 | ~70 | ~160 | ~240 | ~400 | ~600 | ~1000 |
Write Data Point | ~25000 | ~50000 | ~80000 | ~150000 | ~250000 | ~400000 | ~35000 | ~80000 | ~120000 | ~200000 | ~300000 | ~500000 |
Query Requests Per Second | ~25 | ~50 | ~80 | ~150 | ~250 | ~400 | ~75 | ~170 | ~300 | ~480 | ~780 | ~1250 |
Specification Code | influxdata.n1.mxlarge | influxdata.n1.xlarge | influxdata.n1.2xlarge | influxdata.n1.4xlarge | influxdata.n1.8xlarge | influxdata.n1.16xlarge | influxdata.n1.mxlarge_ha | influxdata.n1.xlarge_ha | influxdata.n1.2xlarge_ha | influxdata.n1.4xlarge_ha | influxdata.n1.8xlarge_ha | influxdata.n1.16xlarge_ha |
China | Mainland China | 40.9 | 80.75 | 160.3 | 319.41 | 637.47 | 1273.89 | 113.74 | 224.33 | 445.68 | 888.21 | 1773.29 | 3543.59 |
China (Hong Kong) | 59.86 | 119.71 | 239.41 | 478.81 | 957.47 | 1914.93 | 166.57 | 332.84 | 665.98 | 1331.65 | 2663.29 | 5326.72 |
Asia-Pacific | Japan (Tokyo) | 66.27 | 132.54 | 265.08 | 529.86 | 1059.71 | 2119.41 | 184.18 | 368.66 | 737.17 | 1473.89 | 2947.77 | 5895.83 |
India (Mumbai) | 47.62 | 95.23 | 190.3 | 380.45 | 761.05 | 1521.95 | 132.39 | 264.78 | 529.41 | 1058.36 | 2117.02 | 4233.44 |
Singapore | 59.86 | 119.71 | 239.41 | 478.81 | 957.47 | 1914.93 | 166.57 | 332.99 | 665.98 | 1331.65 | 2663.44 | 5326.72 |
Malaysia (Kuala Lumpur) | 56.87 | 113.74 | 227.47 | 454.78 | 909.56 | 1818.96 | 158.06 | 316.42 | 632.69 | 1264.78 | 2530 | 5060 |
Indonesia (Jakarta) | 60 | 119.71 | 239.56 | 478.81 | 957.47 | 1914.93 | 166.72 | 332.84 | 666.12 | 1331.65 | 2663.29 | 5326.87 |
Europe | Germany (Frankfurt) | 63.29 | 126.42 | 252.69 | 505.23 | 1010.45 | 2020.9 | 175.83 | 351.5 | 702.84 | 1405.53 | 2810.9 | 5621.8 |
UK (London) | 60.15 | 120.3 | 240.45 | 480.6 | 961.2 | 1922.24 | 167.17 | 334.33 | 668.66 | 1336.87 | 2673.74 | 5347.32 |
America | US (Virginia) | 47.77 | 95.53 | 190.9 | 381.8 | 763.44 | 1526.72 | 132.84 | 265.53 | 530.9 | 1061.8 | 2123.59 | 4247.02 |
West America (Silicon Valley) | 61.5 | 122.99 | 245.83 | 491.65 | 983.29 | 1966.57 | 171.05 | 341.95 | 683.89 | 1367.62 | 2735.23 | 5470.45 |
* TSDB for InfluxDB® High-availability Edition stores data in three copies. The instance purchase page shows the standard SSD capacity for a single node. In High-availability Edition, three nodes are used. The actual storage capacity that is allocated to each instance of High-availability Edition is three times the standard SSD capacity for a single node. Therefore, the price is USD 3/month/GB.