Skip to content

docs(flash): explain standby workers next to the workers parameter #902

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
lavanya-gunreddi merged 2 commits into from
Oct 16, 2026
Merged

docs(flash): explain standby workers next to the workers parameter #902

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
480f3c4
docs(flash): explain standby workers next to the workers parameter
justinwlin Oct 15, 2026
58240cc
Update parameters.mdx
lavanya-gunreddi Oct 16, 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
5 changes: 5 additions & 0 deletions flash/configuration/parameters.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,6 +148,11 @@ Controls worker scaling. Accepts either a single integer (max workers with min=0
- `workers=(1, N)`: Avoid cold starts by keeping at least one worker warm
- `workers=(N, N)`: Fixed worker count for consistent performance

<Note>
Runpod also keeps a few standby workers parked for each endpoint so jobs can start quickly with [FlashBoot](/serverless/endpoints/endpoint-configurations#flashboot). The API shows their target count as `workersStandby`, and the [`/health` operation](/serverless/endpoints/operation-reference#health) can list them as ready. Runpod picks this number for you, and you aren't billed for a parked worker until it starts running.
`workers=(0, N)` still scales to zero.
</Note>

### idle_timeout

**Type**: `int`
Expand Down
Loading