Token-Budget-Aware Pool Routing for Cost-Efficient LLM Inference

TL;DR

This paper introduces a token-budget-aware routing method for vLLM fleets that significantly reduces GPU costs by efficiently directing requests based on estimated token budgets, improving resource utilization.

Contribution

It proposes a novel online learning-based routing algorithm that dynamically allocates requests to different pools, optimizing GPU usage without requiring a tokenizer.

Findings

Reduces GPU instances by 17-39% on real-world traces.

Predicts fleet savings using a simple cost model based on traffic fraction and throughput gain.

Achieves substantial cost savings in large-scale LLM inference scenarios.

Abstract

Production vLLM fleets provision every instance for worst-case context length, wasting 4-8x concurrency on the 80-95% of requests that are short and simultaneously triggering KV-cache failures -- OOM crashes, preemption storms, and request rejections. Both problems share a single root cause: configuration-traffic mismatch. We propose token-budget-aware pool routing: estimate each request's total token budget using a self-calibrating per-category bytes-per-token ratio, then dispatch it to one of two vLLM pools -- a high-throughput short pool or a high-capacity long pool -- each right-sized for its workload class. The ratio is learned online via exponential moving average from usage.prompt_tokens feedback, requiring no tokenizer. A closed-form cost model, savings = alpha * (1 - 1/rho), predicts fleet-level GPU savings from two observable quantities: the short-traffic fraction alpha and the throughput gain ratio rho. On traces from the Azure LLM Inference Dataset and LMSYS-Chat-1M serving Llama-3-70B on A100 GPUs, token-budget routing reduces GPU instances by 17-39% (\$1.2-2.0M/yr at 1,000 req/s), with savings verified by a self-contained discrete-event simulator. A case study projecting Qwen3-235B-A22B on AMD MI300X at 10,000 req/s shows \$15.4M/yr in savings. The algorithm adds O(1) dispatch overhead, self-calibrates across content types without a tokenizer, and composes with PagedAttention, continuous batching, and prefill-decode disaggregation.