31–40 of 73 posts
Earlier quoted context omitted.
"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.
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.
Quoted post unavailable.
They quite clearly start out by saying they’re only looking to demonstrate the impact of a specific new DB feature they’ve created, and are using benchmarks that illustrate the difference. They make zero claims that QuestDB is faster than Clickhouse overall, and quite carefully point out that prospective users need to run their own benchmarks on their own data to figure out what DB will work for them.
I have always felt that DB benchmarks are useless, always use your own dataset https://gauravkumar.blog/performance-benchmarks-are-useless....
This is why the commercial offerings do not allow you publish benchmarks.
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.
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.
Earlier quoted context omitted.
Quoted post unavailable.
What an extremely unfair comment. Having read QuestDBs blog, it’s quite clear they’ve taken great pains to point out that a single specific benchmark isn’t the be all and end all of DB analysis. They quite clearly start out by saying they’re only looking to demonstrate the impact of a specific new DB feature they’ve created, and are using benchmarks that illustrate the difference. They make zero claims that QuestDB i…
Are you sure? Just one look at their website says differently.
https://questdb.io/time-series-benchmark-suite/
I don't use these tools. I just wanted to point out that what you're saying is disingenuous.
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.
I wonder what "every effort to be fair" means ? The first thing you could have done is reach out to ClickHouse Community to ask for optimization suggestions
Earlier quoted context omitted.
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.
So, QuestDB is faster or not? I'm puzzled now!
But if you are okay that only limited number of columns to be scanned faster than others ClickHouse comes first.