Problems / LLM serving, medium

One replica owns the hot prefix

A support-agent fleet sends 30 requests a second through a prefix-aware router to 6 model replicas. 85% of requests start with the same 12,000-token system prompt and tool schemas, and the router always sends a prefix to the replica that holds it.

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 ≤ 3 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 6; 2 of them are hidden until then.

  1. As given. The problem’s own traffic, scheduled failures and seed.
  2. Peak hour. 25% more traffic than the problem states, with the same failures.
  3. A slow dependency. The main data store or model answers twice as slowly for part of the run.
  4. A server dies. One replica of the service with the most replicas is killed for part of the run.

The traffic

30 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 Prefix-aware router.Little's law: throughput ≈ concurrency ÷ latency. 200 slots at 50 ms serve about 4,000 req/s.3 replicas × 500 slots · timeout 30 s
Prefix-aware routerInference router (KV-aware)AI app calls it.Calls GPU replica 1, GPU replica 2, GPU replica 3, GPU replica 4, GPU replica 5, GPU replica 6.Routing a session back to the replica that holds its prefix can raise KV-cache hit rates from about 20% to 75%.100000 slots
GPU replica 1Self-hosted serving poolPrefix-aware router forwards to it.GPU servers batch requests together; throughput rises with batch size until memory runs out.4 slots
GPU replica 2Self-hosted serving poolPrefix-aware router forwards to it.GPU servers batch requests together; throughput rises with batch size until memory runs out.4 slots
GPU replica 3Self-hosted serving poolPrefix-aware router forwards to it.GPU servers batch requests together; throughput rises with batch size until memory runs out.4 slots
GPU replica 4Self-hosted serving poolPrefix-aware router forwards to it.GPU servers batch requests together; throughput rises with batch size until memory runs out.4 slots
GPU replica 5Self-hosted serving poolPrefix-aware router forwards to it.GPU servers batch requests together; throughput rises with batch size until memory runs out.4 slots
GPU replica 6Self-hosted serving poolPrefix-aware router forwards to it.GPU servers batch requests together; throughput rises with batch size until memory runs out.4 slots

More llm serving problems