Introducing Dynamo Snapshot, our approach for fast startup for inference workloads on Kubernetes, which reduces startup time from minutes to under 5 seconds. In production inference deployments demand fluctuates over time. Cold-starting inference workloads can take minutes, leaving idle GPUs that generate no tokens and serve no requests. Snapshot leverages GMS to enable concurrent weight restoration over a high-speed interconnect, while using Linux native AIO and parallel memfd restoration to accelerate CRIU restore performance.
NVIDIA Dynamo Snapshot Cuts AI Inference Startup Times to Under Five Seconds
NVIDIA· Updated
NVIDIA announced Dynamo Snapshot, a framework that reduces Kubernetes inference startup times from minutes to under five seconds. By decoupling model weights from process state, the system enables near-instant elastic scaling for large language models without maintaining expensive, idle GPU capacity.
cuda-checkpoint tool to serialize GPU memory. This allows a fully warmed inference worker to resume execution nearly instantly on any node in a cluster.- Startup time
- Under 5 seconds
- Startup speedup (120B model)
- 21x
- Snapshot size (Qwen3-0.6B)
- 6.2 GiB
- Snapshot size (gpt-oss-120b)
- 129 GiB
- Supported engines
- vLLM, SGLang
AI demand is elastic, but the minutes required to load weights often cause SLA violations during spikes. This update extends the NVIDIA Dynamo 1.0 inference OS to address the infrastructure bottleneck that forced providers to over-provision hardware. By unmapping the KV cache, it makes rapid, serverless-style scaling economically viable.
The experimental release supports single-GPU workloads running vLLM or SGLang. Future updates will add support for TensorRT-LLM and multi-node clusters. The snapshot agent is available via Helm to help you implement sub-5-second auto-scaling, with core CRIU optimizations currently pending an upstream merge.
Still wondering? A few quick answers below.
Every HeadsUpAI update is written based on its original source and reviewed before it's published. Read our editorial standards →




