This article compares two popular time-series database (TSDB) products – InfluxDB vs. TDengine – to help you determine which is right for your use case. With industries ranging from IoT to manufacturing generating and collecting a constantly increasing amount of time-series data, the growth of the time series DBMS market over the past five years has not come as a surprise. This popularity has resulted in a large number of time series DB solutions coming on the market, sometimes making it difficult to choose the best time series database for a certain business scenario.
InfluxDB is one of the earliest of the new generation of open-source time-series databases and as such is one of the most commonly found in existing deployments. Its large community and documentation resources are major benefits, but it can suffer from slow performance in some conditions, such as when data sets have high cardinality. TDengine is also an open-source time-series database that differentiates itself with high performance, a distributed cloud-native architecture, and built-in caching, data subscription, and stream processing that simplify the overall system design.
The following table compares the basic information of InfluxDB vs. TDengine.
Basic Info: InfluxDB vs. TDengine
InfluxDB | TDengine | |
---|---|---|
Creator | InfluxData | TDengine |
Initial release | 2013 | 2017 |
Main development language | Go | C |
Main query language | Flux (proprietary) | Standard SQL |
License | MIT | AGPL |
Operating systems | Linux, macOS, and Windows | Linux, macOS, and Windows |
Performance Comparison
Performance is one of the main factors by which time-series databases are compared. Higher performance means more than just faster operations – it also reduces the total cost of ownership for your time-series data operations as fewer hardware resources are required.
According to a performance comparison of InfluxDB vs. TDengine, conducted based on the open-source TSBS framework, TDengine significantly outperforms InfluxDB in all key areas – data ingestion rate, query response time, and disk space usage – while using fewer server-side resources.


As shown in the figures, TDengine provided superior ingestion performance in all scenarios, writing the TSBS data 3.0x to 10.6x faster than InfluxDB. In terms of disk space usage, TDengine and InfluxDB required approximately the same amount of disk space to store the TSBS data for the smaller scenarios. However, in the largest scenario of 10 million devices, InfluxDB occupied 4.5x more disk space.


TDengine also queried the TSBS data much faster than InfluxDB, both in simple and complex scenarios. In the simple rollups category, TDengine responded to queries up to 12 times faster than InfluxDB, and up to 34 times faster in the double rollups category.
- For more information about this performance comparison, see our main blog.
- To review all test results, including steps to reproduce, download the full report.
Conclusion
InfluxDB and TDengine both have rich feature sets and are great choices for processing time-series data. The best choice for your particular scenario may depend on your specific requirements, such as whether SQL support is necessary. TDengine also has significant advantages in terms of performance, giving it the edge in speed- or cost-sensitive use cases.
If you would like to know more about how TDengine can support your enterprise time-series data processing needs, contact us to speak with an account representative.