From Inference Engine to Inference Control Plane: Connecting vLLM, llm-d, and the Evolution of Efficient Distributed LLM Serving
Abstract
Large language model (LLM) inference is evolving from an engine-local optimization problem into a distributed control problem involving reusable state, phase placement, heterogeneous accelerators, networking, autoscaling, reliability, and service-level objectives. This paper connects that transition across peer-reviewed systems research, open-source implementations, and documented production studies. It treats vLLM and llm-d as complementary layers: model-serving engines optimize execution through mechanisms such as PagedAttention, continuous batching, kernels, quantization, and parallelism, while an inference control plane can optimize where, when, and under what policy execution occurs across a fleet. The contribution is synthesis rather than a new benchmark; all reported performance and deployment results remain attributed to their original sources. The combined evidence suggests that the scarce resource in modern inference is shifting from raw FLOPs alone toward managed state, placement, network movement, reliability, and decision quality. We propose an Inference Execution Planner that selects feasible execution plans rather than only endpoints, including aggregated versus disaggregated topology, KV source and transfer action, hardware variant, routing/admission policy, and slower scaling decisions. We also provide a source-local benchmark atlas, a bottleneck-migration taxonomy, practical deployment guidance, an evaluation framework based on SLO-goodput, and research questions for agentic, multimodal, heterogeneous, and resilient inference.
Figures & tables
| Tier | Evidence | Representative sources | How it is used |
| A | Peer-reviewed systems research | Orca; PagedAttention/vLLM; Sarathi-Serve; Splitwise; DistServe; Llumnix; FlashAttention-3; RaidServe | Strongest basis for architectural mechanisms and controlled experimental findings. |
| B | Academic preprints / research prototypes | Mooncake; Preble; MemServe; MInference; Mnemosyne; M*; energy studies | Frontier mechanisms and hypotheses; results remain conditioned on their evaluation settings. |
| C | Open-source implementation and project evidence | vLLM repository and docs; llm-d releases, routing/KV/autoscaling/tracing studies; NVIDIA Dynamo docs | Establishes current capabilities and implementation direction; benchmark results are project-specific. |
| D | Production / cloud-provider reports | Google Vertex routing observations; Tesla/Red Hat/KServe report; AWS and OCI llm-d studies | Evidence of production feasibility and operator constraints; outcomes are organization-reported, not independent causal estimates. |
| System / mechanism | Evaluation setting (abridged) | Reported result | Interpretation used here |
| vLLM / PagedAttention ( Kwon et al., 2023 ) | SOSP 2023 serving evaluation vs FasterTransformer/Orca | 2–4 throughput at similar latency in evaluated settings | Efficient KV memory changes achievable batching and engine goodput. |
| Splitwise ( Patel et al., 2024 ) | Phase-split cluster designs | 1.4 throughput at 20% lower cost in one design; 2.35 throughput at same cost/power in another | Prefill and decode can justify different hardware and resource policies. |
| DistServe ( Zhong et al., 2024 ) | Phase-specific SLO-constrained serving | Up to 7.4 more requests or 12.6 tighter SLOs while 90% meet constraints | Goodput under phase-specific SLOs is more useful than raw throughput alone. |
| Prefix-aware llm-d routing ( Tang et al., 2026 ; llm-d Maintainers, 2026c ) | Llama 3.1 70B, 4 AMD MI300X, project/production report | 3 higher output throughput and 2 faster TTFT vs round-robin | Real traffic can make locality-aware placement materially different from request-count balancing. |
| Predicted-latency routing ( Mitra et al., 2026a ) | Representative MaaS benchmark plus production Vertex AI observations | 43% lower P50 E2E and 70% TTFT improvement in benchmark; up to 40% TTFT/ITL reduction in Vertex | Online predictors can outperform fixed heuristic weights when features reflect queue/cache state. |
| P2P KV sharing ( Guy et al., 2026 ) | GLM-5.2, identical placement comparison | Mean TTFT 7.85 s 2.56 s; 3.80 10.10 req/s | State movement can decouple the best execution endpoint from the cache owner. |
| Bottleneck | Representative mechanisms | What improves | What may become limiting next |
| Autoregressive scheduling | Orca; continuous batching | GPU occupancy; request interleaving | KV memory and batch-state overhead |
| KV memory | PagedAttention; prefix caching | effective batch size; reuse | distributed locality and cache ownership |
| Prefill interference | chunked prefill; P/D separation | TTFT/ITL isolation | transfer bandwidth; pool ratio; queue coordination |
| Distributed locality | Preble; Mooncake; MemServe | avoided recomputation; long-context reuse | hot-cache queues; transfer decision; storage tiers |
| Endpoint selection | cache/load-aware routing; predicted latency | fleet goodput and tail latency | router CPU; stale telemetry; prediction drift |
| Hardware diversity | stage/variant-aware placement | capacity use; phase fit | capability modeling; cross-vendor transfer |
| Dimension | Core metrics | Why it matters |
| User latency | TTFT, TPOT/ITL, E2E P50/P95/P99, deadline/SLO hit rate | Separates startup delay, streaming quality, and tail behavior. |
| Useful capacity | successful req/s, input/output tok/s, SLO-goodput, batch completion rate | Avoids rewarding work that violates the service contract. |
| State efficiency | prefix hit rate, reusable-token ratio, transfer bytes, tier hit rate, recompute avoided | Explains whether capacity comes from execution or state reuse. |
| Resource economics | accelerator-hours, cost/request, cost/SLO-goodput, energy/request, network/storage cost | Connects performance to deployability and sustainability. |
| Reliability / operations | failover time, interruption probability, rollback success, queue age, fairness, control-plane CPU | Measures behavior under faults, saturation, and day-two operations. |
| Horizon | State of practice | Representative capabilities | Research / engineering frontier |
| H0 | Engine efficiency is established | Continuous batching, PagedAttention, optimized kernels, quantization, prefix caching, TP/PP/EP, speculative decoding | Better per-engine capability discovery and workload-specific performance models. |
| H1 | Fleet intelligence is deployable today | Cache/load-aware routing, global KV indexing, P/D orchestration, flow control, autoscaling, tracing, heterogeneous variants | Joint routing/scaling stability, warm-cache-aware rollout, multi-tenant fairness, control-plane scalability. |
| H2 | Execution-plan control is emerging | P2P state movement, learned latency routing, E/P/D, agent-session retention, simulator-guided policy search | Predict topology + state action + hardware + admission as one constrained plan with uncertainty bounds. |
| H3 | General workload-aware planning is open | Composite multimodal graphs, resilient state, multi-region/cluster choices, policy-driven cost/energy/reliability | Common plan interfaces, graph scheduling, failure-aware optimization, trustworthy online learning, reproducible cross-engine benchmarks. |
LLM Serving
Large language model serving studies how to deliver model responses with low latency, high throughput, and efficient use of compute and memory.
See all 211 papers