LLM Serving
LLM: Large Language Model
Overview
Large language model serving studies how to run inference efficiently for many concurrent requests, balancing response speed, throughput, cost, and service-level objectives. Common approaches include continuous batching and prefill–decode scheduling, request routing, and managing or compressing KV caches; newer systems also use disaggregated hardware, speculative decoding, and workload-aware power control. Evaluations use request traces and production-like workloads to measure time to first token, token latency, throughput, quality, and resource use across models and hardware. A central challenge is that workloads and output lengths vary, so policies that improve throughput or cost can worsen tail latency, fairness, or response quality.
Latest papers
216 papers31 papers in the last four weeks, up 94% on the four weeks before. 0.2% of all new papers.
PEEK: Predictive Queue-Informed KV Cache Management for LLM Serving
HAServe: Horizon-Aware Scheduling and Memory Co-Design for Efficient LLM Serving
Regulating Branch Parallelism in LLM Serving
VibeServe: Can AI Agents Build Bespoke LLM Serving Systems?
A Queueing-Theoretic Framework for Stability Analysis of LLM Inference with KV Cache Memory Constraints
Coral: Cost-Efficient Multi-LLM Serving over Heterogeneous Cloud GPUs
When to Think, When to Speak: Learning Disclosure Policies for LLM Reasoning
SPECTRE: Hybrid Ordinary-Parallel Speculative Serving for Resource-Efficient LLM Inference
SGLang and evaluate it across multiple draft--target model pairs, reasoning benchmarks, real-world long-context workloads, and a wide range of batch sizes. Results show that SPECTRE consistently improves large-model serving throughput while causing only minor interference to the native workloads of tail-model services. In large-model deployments, including Qwen3-235B-A22B with TP=8, SPECTRE achieves up to \textbf{2.28 speedup} over autoregressive decoding and up to an additional 66% relative improvement over the strongest speculative decoding baselines. Talk is cheap, we show you the code: https://github.com/sgl-project/sglang/pull/22272.