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.

Sign up for GitHub

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

Jump to bottom

add bash script to run a benchmark #64717

Merged
merged 1 commit into from
May 24, 2024
Merged

add bash script to run a benchmark #64717

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions packages/next-swc/crates/next-build-test/bench.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
#!/bin/bash

# run a benchmark against this binary
# using heaptrack to extract memory
# usage numbers at g-max

set -e

COMMIT=${1:-13d9693808badd4b92811abac5e18dc1cddf2384} # the sha of the commit to benchmark
PAGES=${2:-"/sink,/examples/forms/appearance,/examples/cards,/examples/dashboard,/api/components,/examples/forms/notifications,/sink/new-york,/examples/forms/display,/blocks,/docs/[[...slug]]"} # the list of pages to build

SCRIPTPATH="$( cd -- "$(dirname "$0")" >/dev/null 2>&1 ; pwd -P )"

# build the binary
cargo build --profile release-with-debug --manifest-path "$SCRIPTPATH/Cargo.toml"

# create a temp dir and clone shadcn-ui into it
TMPDIR=$(mktemp -d)
git clone https://github.com/shadcn-ui/ui.git "$TMPDIR"
cd "$TMPDIR/apps/www"
git checkout "$COMMIT"

# install the dependencies and change dir
pnpm install

# heaptrack the binary with the project options in raw mode
heaptrack --record-only "$SCRIPTPATH/../../../../target/release-with-debug/next-build-test" concurrent 12 "$PAGES"
Copy link
Member

@sokra sokra May 15, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of heaptrack you could print out TurboMalloc::memory_usage() which is our own counter of memory usage. That probably makes it a bit faster

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah TBH heaptrack was useful but in this case the overhead will probably be quite brutal when running on CI

"$SCRIPTPATH/../../../../target/release-with-debug/next-build-test" run concurrent 12 999 "$PAGES"

# get most recently created heaptrack profile and run it via heaptrack_print
PROFILE=$(ls -t "$TMPDIR/heaptrack.*" | head -n1)
heaptrack_print "$PROFILE" > "$SCRIPTPATH/result.log"
Loading