3 ms·
postgres isn't known for being fast, quite the opposite if your usecase is one clickhouse can handle (timeseries/olap) most queries are orders of magnitude fas
by gfody 4y ago
postgres isn't known for being fast, quite the opposite
if your usecase is one clickhouse can handle (timeseries/olap) most queries are orders of magnitude faster.
- akulkarni 4y agoTime-series queries are faster on TimescaleDB (built on PostgreSQL) than ClickHouse. https://www.timescale.com/blog/what-is-clickhouse-how-does-it-compare-to-postgresql-and-timescaledb-and-how-does-it-perform-for-time-series-data/ https://www.timescale.com/blog/what-is-clickhouse-how-does-i... Disclaimer: Timescale co-founder
- gfody 4y agoclickhouse 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 (not all olap solutions support timeseries well but clickhouse does, though their actual positioning is modest: https://clickhouse.com/docs/en/faq/use-cases/time-series https://clickhouse.com/docs/en/faq/use-cases/time-series) how much of timescale's performance would you say is inherited from PostgreSQL?
- akulkarni 4y agoclickhouse 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)