Skip to main content
Infrastructure

Model Serving

Model serving is the runtime infrastructure that hosts a trained model and exposes it as an API for low-latency online inference at scale, handling batching, autoscaling, GPU sharing, versioning, and routing.

AIDOLS Research Team · Editorial standards

Full definition

Common serving stacks include NVIDIA Triton, KServe, vLLM (for LLMs), and managed services like SageMaker Endpoints and Vertex AI Online Prediction. Serving is where dynamic batching, paged attention (KV cache), tensor parallelism, and quantized weights translate directly into dollars: a 2x serving efficiency gain on a billion-call workload is a six-to-seven-figure annualized line item.

Why it matters

For most enterprises, lifetime inference cost dwarfs training cost. Serving choice — framework, batching policy, hardware, quantization — is one of the largest levers on GenAI unit economics: the vLLM paper reports 2–4× the throughput of FasterTransformer and Orca at the same latency. Treat serving as a platform discipline, not a config flag.

Example

A SaaS swaps a vanilla HuggingFace endpoint for vLLM with continuous batching and 8-bit quantization, cutting per-token GPU cost 4.6x at unchanged quality.

Next steps

More infrastructure terms

Source & further reading

Primary source: Kwon et al. — "Efficient Memory Management for LLM Serving with PagedAttention" (SOSP) (2023).

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/en/glossary/model-serving/.