Problems / LLM serving, medium

Draft model can’t keep up

Speculative decoding speeds up answers, but the single draft-model GPU is now the bottleneck at 150 requests a second.

Unlock it once for 15 credits; everything inside it is free (runs, changes, Submit, results, hints). Sign in with Google to start; new accounts get free credits.

Your goals

Success ≥ 99%, p99 ≤ 5 s.

Test cases

Like a coding problem, a solution has to pass every case, not just the one it was built for. Submit in the lab runs all 3; 1 of them are hidden until then.

  1. As given. The problem’s own traffic, scheduled failures and seed.
  2. A server dies. One replica of the service with the most replicas is killed for part of the run.

The traffic

150 requests a second for 30 seconds: 100% request (reads).

The system

What each component does in this design, and what calls it. The simulator mimics each one from these settings.

ComponentIts job hereSettings
Load balancerLoad balancerTraffic enters here.Calls AI app.Layer 4 balancers route by IP and port; layer 7 balancers read HTTP and can route by path or header.–
AI appApp serviceLoad balancer forwards to it.Calls Draft model (speculative).Little's law: throughput ≈ concurrency ÷ latency. 200 slots at 50 ms serve about 4,000 req/s.3 replicas × 500 slots · timeout 30 s
Draft model (speculative)Speculative decodingAI app calls it.A small draft model guesses several tokens; the large model checks them in one pass and keeps the ones it agrees with.32 slots

More llm serving problems