-
-
Notifications
You must be signed in to change notification settings - Fork 246
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
Setup CI to run benchmarks and access results #2235
Comments
Just to mention that we should probably be a bit selective with which benchmarks to run. e.g., I don't think we need to run the benchmarks for other libraries, and probably just the Regarding the Nested benchmarks, I think running just the We should probably also reduce warmup and measurement time to 1 second (3 seconds seems like an overkill) to reduce execution time of benchmarks. At the same time, we might want to use Finally, we probably want to check how we're doing comparitively when running multi-threaded vs single-threaded, so we we might want to run |
We could start with just running |
Here's an example of the end result (I ran the test and uploaded to gist manually): https://jmh.morethan.io/?source=https://gist.githubusercontent.com/ghostdogpr/589d379ba2d096afcbf5a27d4298fb16/raw/e98d61fc0a3d87ad7d31b9f17eeb6596a014a19d/jmh-result.json File obtained from running |
It would be nice to run benchmarks:
Then, the job should gather results and upload them somewhere (gist?) so that we could visualize them like this: https://jmh.morethan.io/?source=https://gist.githubusercontent.com/fwbrasil/27c8abec86e947e9719d41a859deb5d2/raw/814ca4ebb3a1294f8dd7bbec9b54ea0957b92434/jmh-result.json
We can probably copy Kyo's CI: https://github.com/getkyo/kyo/blob/main/.github/workflows/bench.yml
The text was updated successfully, but these errors were encountered: