7 ms·

Wait was not TimescaleDB completely leave Clickhouse in the dust both in terms of query performance and compression ? https://blog.timescale.com/blog/what-is-

Wait was not TimescaleDB completely leave Clickhouse in the dust both in terms of query performance and compression ? https://blog.timescale.com/blog/what-is-clickhouse-how-does-it-compare-to-postgresql-and-timescaledb-and-how-does-it-perform-for-time-series-data/ https://blog.timescale.com/blog/what-is-clickhouse-how-does-... I think this series of posts confirms the first law of Benchmarketing - for any system one can come up with "unbiased" benchmark which confirms its superiority

radiospiel 5y ago
The timescale example speaks of 110 mio rows, the blogpost here only has 11 mio rows. And thta is probably only a start…
- pradeepchhetri 5y ago
  I selected only 11M rows for this blog because I used the dataset linked in TimescaleDB docs[0]. The dataset linked in CH docs has 1.2B rows[1]. The goal was to make comparison on dataset which both of the databases agrees upon. [0] https://docs.timescale.com/timescaledb/latest/tutorials/nyc-taxi-cab/ https://docs.timescale.com/timescaledb/latest/tutorials/nyc-... [1] https://clickhouse.com/docs/en/getting-started/example-datasets/nyc-taxi/ https://clickhouse.com/docs/en/getting-started/example-datas...
eatonphil 5y ago
Calling this "benchmarketing" sounds like you're saying the entire thing is disreputable which doesn't seem right. This blog post didn't remotely come off as shilling to me. The author does not (seem to) work for either company. They gave it a shot and shared a result. Whether or not it's a good benchmark or representative for your (anyone's) use case is debatable.
- PeterZaitsev 5y ago
  I was rather referring to original TimescaleDB article which claims what unlike some others these are real benchmarks, and I encourage all benchmark (including ours at Percona) to be taken with a pound of salt because they tend to have implicit, if not intentional biases and have rather real applicability to real world.
  - eatonphil 5y ago
    Makes sense, thanks for clarifying!

radiospiel 5y ago

The timescale example speaks of 110 mio rows, the blogpost here only has 11 mio rows. And thta is probably only a start…

pradeepchhetri 5y ago
I selected only 11M rows for this blog because I used the dataset linked in TimescaleDB docs[0]. The dataset linked in CH docs has 1.2B rows[1]. The goal was to make comparison on dataset which both of the databases agrees upon. [0] https://docs.timescale.com/timescaledb/latest/tutorials/nyc-taxi-cab/ https://docs.timescale.com/timescaledb/latest/tutorials/nyc-... [1] https://clickhouse.com/docs/en/getting-started/example-datasets/nyc-taxi/ https://clickhouse.com/docs/en/getting-started/example-datas...

eatonphil 5y ago

Calling this "benchmarketing" sounds like you're saying the entire thing is disreputable which doesn't seem right. This blog post didn't remotely come off as shilling to me. The author does not (seem to) work for either company. They gave it a shot and shared a result. Whether or not it's a good benchmark or representative for your (anyone's) use case is debatable.

PeterZaitsev 5y ago
I was rather referring to original TimescaleDB article which claims what unlike some others these are real benchmarks, and I encourage all benchmark (including ours at Percona) to be taken with a pound of salt because they tend to have implicit, if not intentional biases and have rather real applicability to real world.
- eatonphil 5y ago
  Makes sense, thanks for clarifying!