Turn it on
CPU resizing is set per template. SetvcpuMax alongside vcpu: vcpu is the minimum a sandbox starts with, and vcpuMax is the most it can grow to. Sandboxes from that template, and sandboxes created from snapshots of them, use the same range.
vcpu_max to sandbox_template_create.
vcpuMax takes whole vCPUs. It must be greater than vcpu, at most 4 times it, at most 32, and within your plan’s vCPU limit. See Growing CPU. Templates without it keep a fixed vCPU count.
You can combine it with live memory resizing on the same template.
How it works
It’s automatic: no API calls, no restarts, and no changes to your code.- Starting: a new sandbox gets the minimum,
vcpu. - Under load: when the sandbox is busy, its CPU allowance rises, up to
vcpuMax. - When idle: once the load drops, the allowance drops back, never below
vcpu.
Billing
You pay for the CPU allowance a sandbox is granted, the same way you pay for memory. While it’s quiet you’re billed at the minimum, while it’s scaled up you’re billed for the larger allowance, and once it drops back you’re billed at the smaller allowance again.Check the range
vcpuCount / vcpu_count is the minimum and vcpuMax / vcpu_max is the ceiling. vcpuMax isn’t set for sandboxes with a fixed vCPU count. Templates and snapshots report the same range. The console shows it as a range, for example 1–4 vCPU.