Our article in question can be found here: https://questdb.io/blog/2022/05/26/query-benchmark-questdb-v...
The intent of the article was to showcase JIT-optimised WHERE clause and we did not use any indexes on QuestDB.
No, QuestDB is not Faster than ClickHouse
11–20 of 73 posts
Re: No, QuestDB is not Faster than ClickHouse
#12Is there an existing named adage for something like "if one creates a benchmark in order to rank general performance of some products, some of those products will ultimately sacrifice general performance in order to optimize for that benchmark"?
https://en.wikipedia.org/wiki/Goodhart's_law
You stated it almost directly.
Re: No, QuestDB is not Faster than ClickHouse
#13Is there an existing named adage for something like "if one creates a benchmark in order to rank general performance of some products, some of those products will ultimately sacrifice general performance in order to optimize for that benchmark"?
[deleted]
Re: No, QuestDB is not Faster than ClickHouse
#14Our article in question can be found here: https://questdb.io/blog/2022/05/26/query-benchmark-questdb-v... The intent of the article was to showcase JIT-optimised WHERE clause and we did not use any indexes on QuestDB.
[deleted]
Re: No, QuestDB is not Faster than ClickHouse
#15Is there an existing named adage for something like "if one creates a benchmark in order to rank general performance of some products, some of those products will ultimately sacrifice general performance in order to optimize for that benchmark"?
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.
Re: No, QuestDB is not Faster than ClickHouse
#16Earlier quoted context omitted.
Well, I don't know how QuestDB works, and I couldn't find anything in the original benchmark, but probably they already have some sort of (geo)index in place? It's really strange to search geo-data by scanning the whole surface of the Earth. The point that Clickhouse outperforms this by just sorting on one axis (and even not using any fancy 2D indices) is reasonable.
I was curious to hear more details about this statement - "while QuestDB utilizes its full indexing strategy to read just a tiny fraction of the actual data". Did QuestDB create indexes in their QuestDB benchmark but just not mention it? Are there geoindexes which are automatically enabled which do help (but are of less value in the general sense from Clickhouse' perspective)?
I don't know how QuestDB is implemented in any detail, but this statement struck me as confused. My understanding is that for this query, QuestDB is performing a full scan of the relevant columns, and the point of the blog post was how fast their JIT engine for filtering makes this.
Re: No, QuestDB is not Faster than ClickHouse
#17This 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
Re: No, QuestDB is not Faster than ClickHouse
#18Our article in question can be found here: https://questdb.io/blog/2022/05/26/query-benchmark-questdb-v... The intent of the article was to showcase JIT-optimised WHERE clause and we did not use any indexes on QuestDB.
No post body was provided.
Re: No, QuestDB is not Faster than ClickHouse
#19[deleted]
Re: No, QuestDB is not Faster than ClickHouse
#20Our article in question can be found here: https://questdb.io/blog/2022/05/26/query-benchmark-questdb-v... The intent of the article was to showcase JIT-optimised WHERE clause and we did not use any indexes on QuestDB.
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.