feat: warm-boot snapshot for the Vercel Sandbox eval runner - #201
Draft
Rodriguespn wants to merge 3 commits into
Draft
feat: warm-boot snapshot for the Vercel Sandbox eval runner#201Rodriguespn wants to merge 3 commits into
Rodriguespn wants to merge 3 commits into
Conversation
Pre-bakes docker + node_modules + the agent base image + the Supabase stack images into a snapshot so per-pair VMs boot warm (dockerd restart + git fetch/checkout + cache-hit pnpm install) instead of cold-provisioning and pulling images on every pair. - scripts/vercel-sandbox.ts: shared VM primitives + coldProvision, extracted so the runner and the builder no longer import each other (breaks a cycle). - scripts/vercel-snapshot.ts: one-shot builder; runs coldProvision + bakes, then tears the prewarmed stack fully down so only images survive into the snapshot (a warm agent must see the same clean docker state as cold). - run-vercel-evals.ts: warm/cold boot branch; --snapshot builds one for this run, --snapshot-id reuses a prebuilt one; default is unchanged (cold). Measured on build-cli-001-bootstrap-app (codex-gpt-5.4-mini, runs=1): cold eval 205s -> warm 131s, snapshot build ~180s, same 7/7 checks cold and warm. Net win requires reuse via --snapshot-id (a per-run build regresses at concurrency >= pairs), so the default stays cold to avoid any CI regression. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Passes --snapshot-id to eval:vercel when the repo variable is set, so the full refresh boots pairs warm from a snapshot built out-of-band. Unset -> cold boots, so this can't regress the default path. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
mattrossman
force-pushed
the
mattrossman/ai-912-spike-vercel-sandbox-runner-for-evals
branch
from
August 14, 2026 15:18
117ec3a to
489b380
Compare
Rodriguespn
changed the title
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
1 participant
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.
Follow-up to #192.
Adds an opt-in Vercel Sandbox warm-boot snapshot to the
run-vercel-evalscontroller, measures the net gain under the same conditions as #192, and importantly, keeps the default path cold so it cannot regress the scheduled refresh.Full refresh at scale: warm vs cold, both concurrency=250 / runs=2:
run-evalsEvery one of the 237 pairs booted warm from the prebuilt snapshot (
vars.EVAL_SNAPSHOT_ID): 0 cold, 0 sandbox failures.The warm run did more pairs (237 vs 220) in less wall-clock, with zero build cost this run (the snapshot was built out-of-band and reused) - ≈13% faster per-pair throughput. The remaining ~28 min is dominated by agent execution + the sequential 2-attempt retry (the separate parallel-attempts lever, not touched here).
The warm run's benchmark pass rate is 194/220 = 88.2%, identical to
main's cold history (194/220 = 88.2%) — the environment change didn't move outcomes.Recommended CI wiring (follow-up, not in this draft)
Keep the scheduled refresh on the default cold path, and add a small "build snapshot" job keyed on
pnpm-lock.yaml+packages/sandbox/Dockerfile+ the pinned CLI/skills versions that builds once and publishes the id (repo/environment variable or artifact);eval-refreshconsumes it via--snapshot-id.