Skip to content

sandboxd: add the 2xlarge tier (8 CPU / 16G) - #150

Merged
CMGS merged 1 commit into
mainfrom
feat/2xlarge-tier
Sep 11, 2026
Merged

CMGS merged 1 commit into
mainfrom
feat/2xlarge-tier

Conversation

@CMGS

@CMGS CMGS commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Carries dc79a79 from feat/desktop-flavor to main on its own: the size table, the Go SDK and MCP option lists, and the deploy/mcp/sdk docs gain 2xlarge (8 CPU / 16 GiB). The desktop flavor image stays on its branch.

The leaderboard host runs main since #149 merged, and the DAX benchmark claims an 8 vCPU / 16 GiB sandbox; without this tier that claim answers 400 unknown size "2xlarge". Verified on the host with this build: a 2xlarge cold boot claims and runs node -v, the small pool is unaffected. Gates on the branch: go vet, types/pool/server tests, sdk/go tests, mcp build.

A GNOME desktop guest with the OSWorld app set needs t3.xlarge-class
memory; xlarge (4 CPU / 8G) was the ceiling. Gates: make go-lint 10x
"0 issues.", make go-test 18 ok.

(cherry picked from commit dc79a79)
@CMGS
CMGS merged commit 0702a01 into main Sep 11, 2026
1 check passed
@CMGS
CMGS deleted the feat/2xlarge-tier branch September 11, 2026 06:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant