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

add CI script for benchmarks #64718

Open
wants to merge 1 commit into
base: arlyon/memory-benchmark-collect-data
Choose a base branch
from

Conversation

arlyon
Copy link

@arlyon arlyon commented Apr 18, 2024

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 #

Copy link
Author

arlyon commented Apr 18, 2024

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.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @arlyon and the rest of your teammates on Graphite Graphite

@arlyon arlyon marked this pull request as ready for review April 18, 2024 10:11
@arlyon arlyon requested review from a team as code owners April 18, 2024 10:11
@arlyon arlyon requested review from jh3y and timeyoutakeit and removed request for a team April 18, 2024 10:11
@ijjk
Copy link
Member

ijjk commented Apr 18, 2024

Allow CI Workflow Run

  • approve CI run for commit: 567a9a7

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

@arlyon arlyon force-pushed the arlyon/memory-benchmark-collect-data branch from d7ccbe0 to 73c3137 Compare April 18, 2024 10:23
@arlyon arlyon requested review from timneutkens, ijjk, shuding, huozhi and a team as code owners April 18, 2024 10:23
@arlyon arlyon force-pushed the arlyon/memory-benchmark-ci-2 branch from 745d903 to 0a47009 Compare April 18, 2024 10:23
@ijjk ijjk added Turbopack Related to Turbopack with Next.js. type: next labels Apr 18, 2024
@arlyon arlyon force-pushed the arlyon/memory-benchmark-collect-data branch from 73c3137 to 3a62b46 Compare April 18, 2024 10:33
@arlyon arlyon force-pushed the arlyon/memory-benchmark-ci-2 branch from 0a47009 to cd39f02 Compare April 18, 2024 10:33
@arlyon arlyon force-pushed the arlyon/memory-benchmark-collect-data branch from 3a62b46 to ac414a8 Compare May 15, 2024 11:25
@arlyon arlyon force-pushed the arlyon/memory-benchmark-ci-2 branch from cd39f02 to 6006cb6 Compare May 15, 2024 11:25
@arlyon arlyon force-pushed the arlyon/memory-benchmark-collect-data branch from ac414a8 to 56b80de Compare May 15, 2024 14:23
@arlyon arlyon force-pushed the arlyon/memory-benchmark-ci-2 branch from 6006cb6 to 567a9a7 Compare May 15, 2024 14:23
- 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 }}
Copy link
Member

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Turbopack Related to Turbopack with Next.js. type: next
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants