-
Notifications
You must be signed in to change notification settings - Fork 44
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 benchmark #102
Comments
We could try utilizing GitHub Action for continuous benchmarking, by comparing to relative regressions. Ref ethereumjs/ethereumjs-monorepo#897 |
High priority IMO. Regressions are devilishly difficult to identify after the fact. The criterion author had a crate targeting CI use cases. Let me try to dig it up. |
IMO the approach to take is to create benchmarks using iai rather than criterion - not that you can't do both. Not sure if there are alternatives. |
As we care performance a lot, it may be necessary to run benchmarks for each PR submission.
The text was updated successfully, but these errors were encountered: