Live data from Hacker News

No, QuestDB is not Faster than ClickHouse

telegra.ph

21–30 of 73 posts

Re: No, QuestDB is not Faster than ClickHouse

#21
post #9

Earlier quoted context omitted.

It's also part of a longer trend of saber rattling between these vendors - there's a history of these types of posts also from TimescaleDB: https://news.ycombinator.com/item?id=29096541

There is a small list of vendors that do not forbid to run benchmarks with their systems. https://cube.dev/blog/dewitt-clause-or-can-you-benchmark-a-d... That is why there is a small subset of vendors that are being 'attacked' by this comparisons.

More and more we start to see why these forbids are in place.

Re: No, QuestDB is not Faster than ClickHouse

#22
post #17

This response illustrates important point - if you're expert in technology A and compare it to technology B, you're not expert in, comparison is very likely to be unfair. I very much would like to see vendors at least to follow Journalist ethics and reach out to their competition for optimization comments and suggestions before publishing it, so others are given a chance to suggest optimizations

Yeah this happens a lot. I like it when people maintain a repo that accepts changes for the comparison

Then you should like https://db-benchmarks.com/

Re: No, QuestDB is not Faster than ClickHouse

#23

Earlier quoted context omitted.

https://en.wikipedia.org/wiki/Goodhart's_law You stated it almost directly.

Oh dear. I did a brief search for 'adage on benchmarking' and only saw Rugg/Feldman benchmarks.

It's also why the only true benchmark is using the thing as it needs to be used - but this is hard to compare because often you need code to work with the tool and vice-versa.

Re: No, QuestDB is not Faster than ClickHouse

#24

This response illustrates important point - if you're expert in technology A and compare it to technology B, you're not expert in, comparison is very likely to be unfair. I very much would like to see vendors at least to follow Journalist ethics and reach out to their competition for optimization comments and suggestions before publishing it, so others are given a chance to suggest optimizations

Agree. Or just load test on your own software, publish how you did it, and let other vendors respond for themselves.

Re: No, QuestDB is not Faster than ClickHouse

#25

Earlier quoted context omitted.

Quoted post unavailable.

I am in fact very proud of my team, who worked very hard on both implementation and the article. It is disappointing to read unfounded insults where we made every effort to be fair.

"while QuestDB utilizes its full indexing strategy to read just a tiny fraction of the actual data"

Can you please elaborate on this?

Re: No, QuestDB is not Faster than ClickHouse

#28

Earlier quoted context omitted.

Quoted post unavailable.

I am in fact very proud of my team, who worked very hard on both implementation and the article. It is disappointing to read unfounded insults where we made every effort to be fair.

No post body was provided.

Re: No, QuestDB is not Faster than ClickHouse

#29
post #25

Earlier quoted context omitted.

I am in fact very proud of my team, who worked very hard on both implementation and the article. It is disappointing to read unfounded insults where we made every effort to be fair.

"while QuestDB utilizes its full indexing strategy to read just a tiny fraction of the actual data" Can you please elaborate on this?

Full disclosure: I am CTO of QuestDB and I took part in JIT implementation. The quote above is not mine, it was written by Clickhouse staff. "utilizes its full indexing strategy" statement is false and is news to me.

Re: No, QuestDB is not Faster than ClickHouse

#30

I have always felt that DB benchmarks are useless, always use your own dataset https://gauravkumar.blog/performance-benchmarks-are-useless....

All benchmarks are always useless, in 90% of the cases. They could maybe give some baseline understanding, but it's important to always do your own benchmarks as your performance can be very different than what the benchmark showed, simply because the data/data structures are slightly different.

Do your own benchmarks people!

Post reply on HN