Repository navigation
Add a headless 16x run of every framework with 25 samples, Chrome pinned to one CPU - #127
Closed
NullVoxPopuli-ai-agent wants to merge 2 commits into
Closed
NullVoxPopuli-ai-agent wants to merge 2 commits into
NullVoxPopuli-ai-agent wants to merge 2 commits into
Conversation
goto and waitForNetworkIdle used puppeteer's 30 s default. At --cpu-throttle=16 with Chrome on one CPU, the solid-1 fan-out "single burst" bench blocks the main thread for about 42 s in one task. Chrome cannot report the last network response during that task, so waitForNetworkIdle stopped the whole run with "Timed out after waiting 30000ms" on sample 23 of 25. Both waits now use --timeout. This changes when the runner gives up, not what it measures. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Result file 9.json. The run used one invocation:
pnpm bench --framework=all --bench=all --headless \
--cpu-throttle=16 --count=25 --timeout=300000 --yes
CPU pinning: every Chrome process (browser, renderer, GPU, workers)
ran on CPU 4 for every bench, through a google-chrome wrapper on
PATH that runs `taskset -c 4`. The runner and the builds ran on
CPUs 0-3 and 5-7, so they did not compete with Chrome.
Other notes:
- TMPDIR was a folder in /dev/shm, because other jobs filled the
root disk and Chrome keeps its shared memory in TMPDIR.
- The 1-minute load average stayed at 3.6 or below on 8 CPUs.
- The run took 3.6 hours. React "Incrementing Render Effect" and
the solid-1 fan-out benches take 25 to 51 s per sample, so the
run needs --timeout above the 60 s default.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
@NullVoxPopuli is attempting to deploy a commit to the NullVoxPopuli's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
results/public/results/9.json: every framework, headless, 16x CPU throttle, 25 samples, with Chrome pinned to one CPU.The run
google-chromewrapper onPATHrantaskset -c 4. The runner and the builds ran on CPUs 0-3 and 5-7.:done.TMPDIRwas a folder in/dev/shm. Other jobs filled the root disk, and puppeteer's--disable-dev-shm-usageputs Chrome's shared memory inTMPDIR.Runner fix
page.gotoandpage.waitForNetworkIdleused puppeteer's 30 s default instead of--timeout. The solid-1 fan-out "single burst" bench blocks the main thread for about 42 s in one task. Chrome cannot report the last network response during that task, so the run stopped withTimed out after waiting 30000ms. Both waits now use--timeout. This changes when the runner gives up, not what it measures.The result file records the
shaof that commit.Why
--timeout=300000React "Incrementing Render Effect" and the solid-1 fan-out benches take 25 to 51 s per sample at this setting. One react sample went past the 60 s default.
🤖 Generated with Claude Code