3 ms·

For perhaps the most comprehensive comparison between InfluxDB and TimescaleDB see this blog post [1] which compares the two DBs on data model, query language,

by avthar 6y ago

For perhaps the most comprehensive comparison between InfluxDB and TimescaleDB see this blog post [1] which compares the two DBs on data model, query language, reliability, performance, ecosystem, operational management, and company/community support. [1]: https://blog.timescale.com/blog/timescaledb-vs-influxdb-for-time-series-data-timescale-influx-sql-nosql-36489299877/ https://blog.timescale.com/blog/timescaledb-vs-influxdb-for-...

pauldix 6y ago
This comparison is vs. InfluxDB. This thread is about a new project called InfluxDB IOx. It's under development and we're not producing builds, so any kind of operational comparison would be very premature. Its architecture is dramatically different than InfluxDB. You can do a comparison of the design goals. Read the post this thread refers to. I think you'll find it has very different goals than Postgres, an OLTP database, and Timescale, which is built on top of it.
- avthar 6y ago
  Thank you for clarifying, OP's original comment refers to TimescaleDB vs InfluxDB hence the comparison blog between the two. As you note, a comparison between InfluxDB IOx and TimescaleDB is not possible at this time, due InfluxDB IOx being still under development and unavailable for comparison, so that blog is the next best thing for developers looking for answers today.
valyala 6y ago
It would be great to see similar comparison for TimescaleDB vs VictoriaMetrics :) There are some benchmarks ([1], [2], [3]) that compare performance and resource usage between TimescaleDB, InfluxDB and VictoriaMetrics, but these benchmarks may be outdated. [1] https://medium.com/@valyala/when-size-matters-benchmarking-victoriametrics-vs-timescale-and-influxdb-6035811952d4 https://medium.com/@valyala/when-size-matters-benchmarking-v... [2] https://medium.com/@valyala/high-cardinality-tsdb-benchmarks-victoriametrics-vs-timescaledb-vs-influxdb-13e6ee64dd6b https://medium.com/@valyala/high-cardinality-tsdb-benchmarks... [3] https://medium.com/@valyala/insert-benchmarks-with-inch-influxdb-vs-victoriametrics-e31a41ae2893 https://medium.com/@valyala/insert-benchmarks-with-inch-infl...
- avthar 6y ago
  Hi valyala (cofounder of VictoriaMetrics) — I know we’ve talked about this several times before already, so you should know — those benchmarks you linked are from 2018. They pre-date many key features in TimescaleDB, including features like native compression, which invalidate many of those findings. So they aren’t really relevant or valid anymore. Just don’t want people to draw wrong conclusions. (Disclaimer: I work at Timescale)

by avthar 6y ago

pauldix 6y ago

This comparison is vs. InfluxDB. This thread is about a new project called InfluxDB IOx. It's under development and we're not producing builds, so any kind of operational comparison would be very premature. Its architecture is dramatically different than InfluxDB. You can do a comparison of the design goals. Read the post this thread refers to. I think you'll find it has very different goals than Postgres, an OLTP database, and Timescale, which is built on top of it.

avthar 6y ago
Thank you for clarifying, OP's original comment refers to TimescaleDB vs InfluxDB hence the comparison blog between the two. As you note, a comparison between InfluxDB IOx and TimescaleDB is not possible at this time, due InfluxDB IOx being still under development and unavailable for comparison, so that blog is the next best thing for developers looking for answers today.

valyala 6y ago

It would be great to see similar comparison for TimescaleDB vs VictoriaMetrics :) There are some benchmarks ([1], [2], [3]) that compare performance and resource usage between TimescaleDB, InfluxDB and VictoriaMetrics, but these benchmarks may be outdated. [1] https://medium.com/@valyala/when-size-matters-benchmarking-victoriametrics-vs-timescale-and-influxdb-6035811952d4 https://medium.com/@valyala/when-size-matters-benchmarking-v... [2] https://medium.com/@valyala/high-cardinality-tsdb-benchmarks-victoriametrics-vs-timescaledb-vs-influxdb-13e6ee64dd6b https://medium.com/@valyala/high-cardinality-tsdb-benchmarks... [3] https://medium.com/@valyala/insert-benchmarks-with-inch-influxdb-vs-victoriametrics-e31a41ae2893 https://medium.com/@valyala/insert-benchmarks-with-inch-infl...

avthar 6y ago
Hi valyala (cofounder of VictoriaMetrics) — I know we’ve talked about this several times before already, so you should know — those benchmarks you linked are from 2018. They pre-date many key features in TimescaleDB, including features like native compression, which invalidate many of those findings. So they aren’t really relevant or valid anymore. Just don’t want people to draw wrong conclusions. (Disclaimer: I work at Timescale)