Use bencher #539
Merged
Use bencher #539
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The more I look at the website the less I like it. Anyway we can use this for now and when we have time we could fix the benchmark action to parse criterion output (or do what critcmp does to get more detailed state) |
robert3005
approved these changes
Aug 2, 2024
|
Ok, I think maybe we could use bencher cli and build our own graphs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Trying out bencher.dev, here's a dashboard link:
https://bencher.dev/perf/vortex?report=30841f3c-fcbb-4cdc-930d-13c5e103b5a7&branches=c60fea65-8440-45ed-9f5a-586b9363a67d&testbeds=228d0d7b-dbcd-4483-9b97-f318d448c5aa&benchmarks=aa9da1cb-2f07-4c82-8e24-df4d1b2bd618%2C068a3433-dd6e-454e-9a48-c1f78b11ec58%2C12fb3e97-b42d-4359-be24-3ca947a92ec0%2Cf8ffab38-a93c-4289-b29c-2e9c79ed6ea0&measures=2c3aeb1c-a621-4c2f-a220-8b1204a119ba&start_time=1720019326000&end_time=1722611387000&clear=true&key=true&reports_per_page=4&branches_per_page=8&testbeds_per_page=8&benchmarks_per_page=8&plots_per_page=8&reports_page=1&branches_page=1&testbeds_page=1&benchmarks_page=1&plots_page=1
I changed the schedule to run on all pushes to develop to make testing quicker, we can switch it back to scheduled daily if we find that it's using up too many resources