ci: add benchmark report generation #57
Merged
Conversation
This file contains hidden or 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
Signed-off-by: Ignacio Hagopian <[email protected]>
jsign
force-pushed
the
jsign-ci-bench
branch
from
072b9f4 to
95d17da
Compare
kevaundray
approved these changes
Sep 7, 2023
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.
This PR adds a GH action that generates a historical timeline and a per-action run report of existing benchmarks on every merge to
master.We use free CI machines, so things can be somewhat noisy for activating automatic alerting without setting an absurd threshold of 40%. We can try to watch plots occasionally and see if this is useful.
I had to manually create a
gh-pagesbranch to prepare a bit of the stage for the action to push the generated website to the GH pages automatically.Context: I've discovered a gnark-crypto perf regression while experimenting with an idea in this repo while running benchmarks locally! I hope this automatic report can get us an earlier signal in a similar situation.