-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Pinot benchmark does not have indices. #37
Comments
What indices to add? |
I have found that people from Pinot tried to add a benchmark version with indices but did not submit it: |
If you can take these changes and make them ready for a pull request, it will be helpful. |
@alexey-milovidov https://docs.pinot.apache.org/basics/indexing Can you please bump up the pinot version to 0.12.1? |
Yes, ClickBench can install any version; please edit this file: https://github.com/ClickHouse/ClickBench/blob/main/pinot/benchmark.sh Then you can send the results, or we can run it. |
okay.. Let me take a stab it. I am not a pinot expert. I am trying to evaluate Pinot vs clickhouse for my use case with my own data. This benchmark is a good start. As per this blog 'https://startree.ai/blog/a-tale-of-three-real-time-olap-databases', pinot performs better than clickhouse. Nevertheless, let me read about pinot indexes before I come up with suggestions. |
We stumbled upon this article and found many factual errors and misrepresentations. We did not find any reproducible scenario where Pinot can be faster than ClickHouse. |
The major selling point of Pinot is star tree index. Any comparison that doesn't leverage star tree index is invalid. |
@wisercoder Fair enough. Unfortunately, none of the guys at ClickHouse is an expert in Pinot tuning. Feel free to send a PR that adds indices to Pinot's ClickBench DDL. I am happy to try it out and update benchmark results. |
I am not a user of Pinot so unfortunately I cannot help in this case.
But it seems like it should have indices.
The text was updated successfully, but these errors were encountered: