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

Make Benchmark Tests Run as part of CI for Pull-Requests #44

Open
baldawar opened this issue Sep 13, 2022 · 3 comments
Open

Make Benchmark Tests Run as part of CI for Pull-Requests #44

baldawar opened this issue Sep 13, 2022 · 3 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@baldawar
Copy link
Collaborator

What is your idea?

Right now its kind of annoying to ask for benchmark results as part of each pull-requests. Ideally, we'd have benchmarks run as part of the PR or on-command whenever someone wants it before merging a change.

This would have made the optimization PRs like #37 and #39 easier to merge in. Also, it reduces one more friction point for any future pull-requests.

Would you be willing to make the change?

Maybe

Additional Context

When we get this working, we should make sure benchmarks are only ever run as PR and not part of regular builds (where something running for 6~7 mins is painfully slow for development cycles).

@baldawar baldawar added enhancement New feature or request good first issue Good for newcomers labels Sep 13, 2022
@embano1
Copy link
Member

embano1 commented Sep 27, 2022

I can help with the GHA part of this (including a small tweak to cancel long-running jobs such as benchmarks when new commits are pushed to a PR. Since I'm not an expert in Java benchmarking and the tooling, e.g. which output to use, creating +/- comparisons, etc. it would be great if someone could point me in the right direction so I can create the PR.

@timbray
Copy link
Collaborator

timbray commented Sep 27, 2022

Hmm, I agree in principle but I think people shouldn't send us PRs that have big performance penalties because that will never be OK for Ruler. So I'd like to have some mechanism to provide an incentive to make this clear to a contributor. Maybe it's enough to write it into our submission guidelines or template?

@baldawar
Copy link
Collaborator Author

baldawar commented Sep 29, 2022

The default template does ask for benchmarks which we can keep as it. The action here should help ensure as folks push additional updates to their PR, the github actions are good enough.

On steps to implement this, I suspect it'll be like

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants