> We're built on Clickhouse (instead of Postgres), so most queries are orders of magnitude faster.
Woah woah dems fightin words. Is this true?
Woah woah dems fightin words. Is this true?
Results of query benchmarking between TimescaleDB [built on PostgreSQL] and ClickHouse. TimescaleDB outperforms in almost every query category
I don’t think that post says what you think it says ;-)(Disclaimer, Timescale co-founder)
if your usecase is one clickhouse can handle (timeseries/olap) most queries are orders of magnitude faster.
https://www.timescale.com/blog/what-is-clickhouse-how-does-i...
Disclaimer: Timescale co-founder
how much of timescale's performance would you say is inherited from PostgreSQL?
clickhouse is more generally olap and not suitable for oltp, you could call it an olap+timeseries solution similarly to how you position timescale as oltp+timeseries
You are correct, TimescaleDB is time-series + OLTP. But I would argue that ClickHouse is just OLAP, but is better at time-series than other OLAP. But maybe now I am splitting hairs (and my apologies if I am). how much of timescale's performance would you say is inherited from PostgreSQL?
The performance areas where TimescaleDB shines is mostly stuff we have built. But the reliability, tooling, and ecosystem are mostly inherited from Postgres (which I think is a very good thing)