-
Notifications
You must be signed in to change notification settings - Fork 0
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
How can I submit or request a benchmark report? #2
Comments
Hi @tisonkun thanks for reaching out and your interest in our ranking. We are always happy to include new databases in the ranking. For adding new results, the benchmarks are executed via our benchmarking platform to ensure the same benchmark process and (as close as possible) configuration for all databases. In addition, our platform ensures the metadata collection for transparency and reproducibility. Since you already did benchmarks against GreptimeDB, is there a TSBS fork with a GreptimeDB binding publicly available? looking forward to continue the discussion! |
@seybi87 Thanks for your reply! Glad to see that you're interested in adding new databases.
Yes. We have a TSBS fork at https://github.com/GreptimeTeam/tsbs and we upload the result at https://github.com/GreptimeTeam/greptimedb/blob/main/docs/benchmarks/tsbs/v0.7.0.md.
This is reasonable. You may check the fork and result above to see what difference to your process so that we can align on benchmarking. |
This file lists commands we use to run the benchmark. Note that it doesn't support using this single script to execute the benchmark. We have a data loader for GreptimeDB but don't have a dedicated query binding for GreptimeDB. We use the InfluxDB query binding to run queries. We added some HTTP headers in its request to make it compatible with our DB. |
Hi here!
I'm working at @GreptimeTeam. We built a time-series database GreptimeDB and a cloud service GreptimeCloud.
We did benchmark ourselves on tsbs and wonder how we can submit the result to benchANT or request you experts to do a benchmark on our product.
Looking forward to your feedback :D
The text was updated successfully, but these errors were encountered: