3 ms·
I benchmarked ClickHouse vs. Timescale, Citus, Greenplum and Elasticsearch for a real-time analytics application. With a couple hours learning for each (althoug
by fiddlerwoaroof 5y ago
I benchmarked ClickHouse vs. Timescale, Citus, Greenplum and Elasticsearch for a real-time analytics application. With a couple hours learning for each (although I’ve used Postgres extensively and so Postgres-backed databases had a bit of an advantage), ClickHouse’s performance was easily an order of magnitude or two better than anything except ES. ES had its own downsides with respect to the queries we could run (which is why we were leaving ES in the first place).
- someguy101010 5y agoWhat did you end up going with?
- fiddlerwoaroof 5y agoClickHouse deployed to EKS with Clickhouse operator
- eastdakota 5y agoCloudflare’s analytics have been powered by Clickhouse for a long time. And I was an early investor in Timescale. They’re both excellent products.
- fiddlerwoaroof 5y agoYeah, I was a little disappointed because I was rooting for Timescale myself. And, maybe if I had spent more time optimizing, I could have made Timescale work but, between our experiments and Cloudflare’s blog post about migrating from Citus to ClickHouse, ClickHouse seemed like the one most likely to hold up for our production workloads.
- germandiago 5y agoI know of a database that claims to perform even faster than that one, It is commercial, though. For very massive data, in a time-series setup basically. https://www.hydrolix.io/ https://www.hydrolix.io/
- qoega 5y agoFrom docs it seems they use forked ClickHouse code.
- germandiago 5y agoAs far as I understand, they use a part as a frontend, not as a full engine for everything.