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
add CI script for benchmarks #64718
base: arlyon/memory-benchmark-collect-data
Are you sure you want to change the base?
add CI script for benchmarks #64718
Conversation
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
d7ccbe0
to
73c3137
Compare
745d903
to
0a47009
Compare
73c3137
to
3a62b46
Compare
0a47009
to
cd39f02
Compare
3a62b46
to
ac414a8
Compare
cd39f02
to
6006cb6
Compare
ac414a8
to
56b80de
Compare
6006cb6
to
567a9a7
Compare
- name: Build binary | ||
run: cargo build --profile release-with-debug --manifest-path $GITHUB_WORKSPACE/packages/next-swc/crates/next-build-test/Cargo.toml | ||
- name: Run benchmark | ||
run: bash bench.sh 29de71d77fd3db93c33cc3886c64a32ad889278f ${{ matrix.pages }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think the commit should be hard-coded?
What?
See below for the branches this is based on. This PR adds a run to the CI with manual trigger so that we can collect data on it. Once the other two merge, I will begin testing this PR. Still need to validate that the artifacts upload as expected.
Why?
We want to run some consistent benches on memory usage so we can measure over time.
How?
Closes NEXT-
Fixes #