LinkedIn analytics tracking pixel for AIDOLS AI consulting website performance measurement
Infrastructure

Continuous Batching

Continuous batching is an inference scheduling technique that adds and removes requests from a GPU batch every decoding step, instead of waiting for all requests in a static batch to finish.

Full definition

Static batching wastes GPU cycles because short requests sit idle waiting for long ones. Continuous batching (also called iteration-level scheduling, introduced in Orca, OSDI 2022) evicts finished requests every step and admits new ones into the freed slots. Combined with paged attention (vLLM, 2023), this raises GPU utilization from 30-40% to 70-90% on real workloads — typically a 4-23x throughput win over static batching at the same latency.

Why it matters

Continuous batching is now table stakes for any serious LLM inference stack (vLLM, TensorRT-LLM, SGLang, TGI). Buyers comparing self-hosted GPU economics should ask which serving engine the vendor uses; teams still on static batching are paying 4-10x more per token.

Example

A SaaS company switches from a custom Triton server to vLLM for Llama 3 70B serving; throughput rises from 600 to 4,800 tokens/sec on the same 8xH100 node, dropping cost-per-million-tokens from $1.20 to $0.18.

Source & further reading

Primary source: Yu et al. — "Orca: A Distributed Serving System for Transformer-Based Generative Models" (OSDI) (2022).

Citation policy: this entry is part of the AIDOLS AI Implementation Glossary and may be quoted for research, journalism, and education with attribution to aidolsgroup.com/sv/glossary/continuous-batching/.