Skip to content

fix(sandbox): correct the E2B build default in the Pi sizing doc #9477

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

Merged
waleedlatif1 merged 2 commits into from
Oct 30, 2026
Merged

fix(sandbox): correct the E2B build default in the Pi sizing doc #9477

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e36be99
fix(sandbox): correct the E2B build default in the Pi sizing doc
waleedlatif1 Oct 30, 2026
16ebf3e
fix(sandbox): clarify the Pi sizing sentence
waleedlatif1 Oct 30, 2026
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
22 changes: 10 additions & 12 deletions apps/sim/lib/execution/remote-sandbox/pi-resources.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,22 +1,20 @@
/**
* vCPU and RAM for the Pi sandbox, shared by both provider builds and by sandbox
* pricing. The two providers had already drifted here. Daytona asked for 4 CPU / 8 GB
* while the E2B template asked for nothing and inherited its base default of
* 2 vCPU / 512 MB — a 16x memory gap between the provider Pi normally runs on and
* the one it fails over to, which would surface as the agent being killed on E2B
* for work that succeeded on Daytona.
* pricing, so Pi gets the same machine on the provider it fails over to as on the one
* it normally runs on. A template built without explicit sizes gets E2B's build default
* of 2 vCPU / 1 GiB, an eighth of the memory Pi gets on Daytona.
*
* 512 MB is the real problem: the Pi CLI is a Node process holding an LLM
* Memory is the dimension that matters: the Pi CLI is a Node process holding an LLM
* context, running beside a `git clone` of the user's repository, and Node has no
* graceful behaviour at that ceiling — it is OOM-killed, which reaches the user
* graceful behaviour at its memory ceiling — it is OOM-killed, which reaches the user
* as an opaque agent failure rather than a diagnosable one.
*
* Memory is at E2B's Professional maximum (8192 MB per build) and CPU is half of
* its 8 vCPU maximum; the minimum is 1 vCPU / 512 MB. Sizing is per-second billed against allocated
* resources rather than used ones, so this costs roughly 3x the previous E2B
* default per sandbox-second. On the compute-bound phases that is close to
* neutral — the work finishes proportionally sooner — but Babysit deliberately
* idles between review polls, and idle seconds bill at the same rate. Lower
* its 8 vCPU maximum. Sizing is per-second billed against allocated resources rather
* than used ones, so this costs roughly 3x the E2B build default per sandbox-second.
* On the compute-bound phases that is close to neutral — the work finishes
* proportionally sooner — but Babysit deliberately idles between review polls, and
* idle seconds bill at the same rate. Lower
* {@link PI_SANDBOX_CPU_COUNT} first if that idle time proves dominant: vCPU is
* ~3x the hourly rate of a GB of RAM, and RAM is the dimension that prevents
* hard failures.
Expand Down
Loading