Skip to content

Mark automatic sizing as preview #147

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
flybayer merged 1 commit into from
Oct 23, 2026
Merged

Mark automatic sizing as preview #147

Show file tree
Hide file tree
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
4 changes: 4 additions & 0 deletions concepts/sandboxes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -256,6 +256,10 @@ Sandboxes don't take `instance_size`, `ami` or `storage`. See [SandboxStepInfras

### Automatic sizing

<Note>
Automatic sizing is in preview. [Contact support](/contact-support) to share feedback.
</Note>

Set `cpu`, `memory` or `disk` to `auto` and Ravion sizes the sandbox from the step's earlier runs. `auto` needs `interruptible: true` on the same step; a step without it must set fixed values, and the pipeline won't save otherwise.

- The first run gets 4 vCPU, 16 GiB of memory and 40 GiB of disk.
Expand Down
4 changes: 4 additions & 0 deletions github-actions/runners.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,6 +138,10 @@ Mark jobs that are safe to run twice as `interruptible=true`, such as tests, lin

### Automatic sizing

<Note>
Automatic sizing is in preview. [Contact support](/contact-support) to share feedback.
</Note>

Stop guessing machine sizes. Set `cpu`, `memory` or `disk` to `auto` and Ravion sizes the sandbox for you.

```yaml
Expand Down
Loading