[zepolen]

As someone who has used both in production environments under various workloads, I can, without a doubt, tell you that Clickhouse spanks the crap out of TimescaleDB.

The only use case where TimescaleDB is more useful is the ability to mutating/deleting single rows but even there, Clickhouse offers some workarounds at the expense of a little extra storage until a compaction is run similar to VACUUM.

Clickhouse is to TimescaleDB what Nginx was to Apache.

[csdvrx]

> I can, without a doubt, tell you that Clickhouse spanks the crap out of TimescaleDB.

Same. I'm ready to believe my experience is not representative, but I've rarely heard something different after talking to people who've seriously evaluated both.

> Clickhouse is to TimescaleDB what Nginx was to Apache.

Perfect comparison. Except I don't remember Apache cooking some tests to pretend they are faster than nginx, or astroturfing communities :)

Different tools serve different purposes, simple as that.

If TimescaleDB or Apache does the job for you, stick with them.

When you will want to scale / increase performance or just rewrite, chose the better option of the day.

In 2021, Clickhouse should be a recommended default, like nginx.

[PeterZaitsev]

I think both Clickhouse and TimeScaleDB are great systems with different design goals and approaches. Specifically I think Clickhouse is much better suited to "Event Logs" than "Metrics" storage (Clickhouse Inspired VM does well in this regard)

I would just encourage all vendors to be more humble positioning their benchmarks. In my practice production behaviors for better or worse rarely resemble benchmark results

[eatonphil]

What is "Clickhouse Inspired VM"?

[PeterZaitsev]

Hm. Not sure why My previous response is marked as dead, I guess VM is swear word It refers to V-I-CTO-R-I-A Metrics

[PeterZaitsev]

VictoriaMetrics https://victoriametrics.com/