llm-d/llm-d
Achieve state of the art inference performance with modern accelerators on Kubernetes
llm‑d – High‑Performance Distributed LLM Inference on Kubernetes
What it is
- An open‑source stack that sits on top of model servers such as vLLM and SGLang and adds production‑grade orchestration, routing, and cache management for large‑language‑model (LLM) inference.
- Built for cloud‑native environments (Kubernetes, Helm) and backed by a CNCF Sandbox project founded by Red Hat, Google Cloud, IBM Research, CoreWeave and NVIDIA.
Core capabilities
| Area | What llm‑d adds |
|---|---|
| Intelligent routing | Prefix‑cache‑aware and load‑aware load‑balancing; experimental latency‑prediction scheduler to cut latency and boost throughput. |
| KV‑cache management | Tiered off‑loading of the attention KV cache to CPU or disk, with a global index that lets multi‑turn requests keep a larger working set. |
| Large‑model serving | Prefill/decode disaggregation and wide expert‑parallelism that spreads massive models (e.g., DeepSeek‑R1, GPT‑OSS‑120B) across fast inter‑connects. |
| Operational excellence | Flow‑control for multi‑tenant traffic, SLO‑aware autoscaling, and active‑active HA to keep services stable at scale. |
| Batch processing | OpenAI‑compatible batch APIs and async pipelines for offline workloads, maximizing hardware utilisation. |
Performance highlights (as reported in the README)
- 3× higher output throughput & 2× faster time‑to‑first‑token (TTFT) on Llama 3.1 70B with prefix‑cache routing (4× AMD MI300X).
- 40 % TTFT/ITL reduction using predicted‑latency scheduling on NVIDIA GPUs.
- Up to 70 % more tokens / sec with prefill/decode disaggregation (GPT‑OSS on AWS B200).
- 50 k tokens / sec cluster throughput with wide expert‑parallelism on a 16×16 NVIDIA B200 mesh.\nHow you would use it
- Deploy – Follow the Quick‑Start guide to install the Helm charts on a Kubernetes cluster (any cloud or on‑prem). The stack provisions the router, cache manager, and model‑server pods automatically.
- Configure – Choose a “well‑lit path” (e.g., Optimized Baseline, Tiered Prefix Cache, Wide Expert‑Parallelism) that matches your model size and hardware accelerator (NVIDIA, AMD, Intel, Google TPU, etc.).
- Run – Send inference requests via the provided OpenAI‑compatible REST endpoint or the batch API. llm‑d will route traffic, manage KV‑cache tiers, and scale pods based on real‑time latency signals.
- Monitor – Built‑in Prometheus metrics and SLO‑aware autoscaling let you keep an eye on throughput, latency, and resource utilisation.
Who benefits
- Enterprises that need to serve many concurrent LLM users with low latency and predictable cost.
- ML‑ops teams looking for a reproducible, cloud‑native way to run state‑of‑the‑art models on heterogeneous accelerators.
- Research labs that want to benchmark new models or inference tricks without hand‑tuning Kubernetes deployments.
Getting started
- Read the Quickstart Guide: https://llm-d.ai/docs/getting-started/quickstart
- Pick a starter recipe from the Well‑Lit Paths documentation (e.g.,
optimized-baseline). - Deploy with Helm (the repo provides version‑pinned charts). The README points to the releases page for exact chart versions.
Community & contribution
- CNCF‑sanctioned project with a public Slack, bi‑weekly stand‑ups, SIGs, and a full contribution guide.
- Apache 2.0 license – free for commercial and academic use.
All details above are taken directly from the repository’s README; no additional features have been inferred.
Related
- Project
- Project
- Project
- Project
- Project