Idle machines
An idle machine is a provisioned server that’s powered on and ready but not currently running a game session. It’s on standby, waiting to be allocated to the next match. Keeping a few machines idle means a new session can start almost instantly, because the server is already running rather than being provisioned from scratch.
Don’t confuse idle with downtime. An idle machine is healthy and ready — it just isn’t needed yet. Downtime is when machines are unavailable and sessions can’t start. Idle is a choice; downtime is a failure.
Do idle machines cost money?
Yes — that’s the catch. An idle machine still consumes a reserved slot, power, and (on cloud) a per-hour charge whether or not a player is on it. The trade-off is speed vs. spend:
- Too few idle machines → players wait while a new server provisions (cold start), or get queued.
- Too many idle machines → you pay for capacity nobody is using, especially during off-peak hours.
The cost of idle capacity is one of the biggest hidden line items in game server hosting. A fleet sized for evening peak sits mostly idle at 4am, and on fixed or reserved models you pay for it regardless.
Idle machines vs. warm pools
A warm pool is idle capacity used deliberately. Instead of leaving whole machines idle, an orchestrator keeps a small, configurable buffer of pre-started containers ready to accept players, so session start time stays near-instant — then refills the pool as sessions are allocated. It’s the controlled version of “keep some machines idle,” tuned in real time to demand rather than provisioned statically.
How orchestration reduces idle cost
The goal is to keep just enough capacity warm for fast starts without paying for a fleet that sits empty. Modern game server orchestration does this with:
- Per-second billing — you pay for sessions that run, not for machines that idle. Capacity released the moment a match ends stops costing you.
- Auto-scaling and cloud-bursting — a baseline of reserved capacity handles steady load; demand spikes burst into on-demand capacity and release afterward, so idle headroom stays small.
- Right-sized warm pools — a thin warm buffer for instant starts instead of large standing idle fleets.
Gameye bills per second on active sessions and manages warm pools dynamically, so studios get fast session starts without paying for a fleet that sits idle through the night.
Frequently asked questions
What is an idle machine? A server that’s provisioned and running but not currently hosting a game session — ready to be allocated, but waiting. Keeping some machines idle lets new sessions start instantly instead of waiting for a server to provision.
Do idle servers cost money? Yes. An idle machine still consumes a reserved slot, power, and (on cloud) per-hour charges whether or not a player is connected. Minimising idle capacity while keeping starts fast is a core cost-optimisation problem in game hosting.
What’s the difference between an idle machine and a warm pool? A warm pool is idle capacity used deliberately — a small, configurable buffer of pre-started containers kept ready for instant session starts and refilled as demand rises. It’s the tuned version of leaving machines idle, sized to demand rather than provisioned statically.
How do you reduce idle server costs? Use per-second billing so you pay for active sessions not idle capacity, auto-scale and cloud-burst so idle headroom stays small, and keep a thin warm pool instead of large standing idle fleets.