Skip to content
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

Continuous Benchmarking #3084

Closed
1 of 4 tasks
Tracked by #3428 ...
BohuTANG opened this issue Nov 25, 2021 · 4 comments
Closed
1 of 4 tasks
Tracked by #3428 ...

Continuous Benchmarking #3084

BohuTANG opened this issue Nov 25, 2021 · 4 comments
Labels
C-testing Category: testing
Milestone

Comments

@BohuTANG
Copy link
Member

BohuTANG commented Nov 25, 2021

Summary

DuckDB's benchmarking are very professional here https://duckdb.org/benchmarks/index.html, thanks to DuckDB for providing such a good testing style :D

Follow the style, databend can also integrate tests:

  • Benchmark runner #3263
  • Provide the hardware(container) for the runner, this can be based on our perf test
  • Run the runner for each nightly version and collect the results to a database(DuckDB using itself for this result stored)
  • Show the results on the website for each nightly

References:

  1. DuckDB website scripts
  2. DuckDB benchmark runner
@BohuTANG BohuTANG added the C-testing Category: testing label Nov 25, 2021
@ZhiHanZ
Copy link
Collaborator

ZhiHanZ commented Nov 25, 2021

Possible settings:

  • 2 workers (4vCPU + 4Gi RAM) run on cloud to benchmark on a medium size dataset (ontime small is fine for now)
    Need to test the following spec
  1. test the performance on S3 storage type (COPY, INSERT, aggregation)
  2. test the performance on local disk (INSERT, aggregation)

@sundy-li
Copy link
Member

sundy-li commented Feb 17, 2022

Rust benchmark graph: https://perf.rust-lang.org/

@PsiACE
Copy link
Member

PsiACE commented Mar 28, 2022

https://github.com/datafuselabs/databend-perf/ contains numbers and ontime benchmarks, run on a XXXLarge machine, and collects performance data for nightly releases.

  • Provide the hardware(container) for the runner, this can be based on our perf test
  • Run the runner for each nightly version and collect the results to a database

@ZhiHanZ
Copy link
Collaborator

ZhiHanZ commented Apr 12, 2022

I think it could be closed? @BohuTANG

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-testing Category: testing
Projects
None yet
Development

No branches or pull requests

5 participants