Watch requests flow through the fleet, then open the playground to try it.
Prefill processes the prompt; decode generates the response.
No batches in flight.
Simulated progress per batch. Completed batches leave the list.
Ready · 24 GPUs available
Same prefix. Less prefill.
Compare two batches on a separate 1-GPU replica. Your fleet keeps running.
Starting an independent comparison.
Cold · simulated prefill
Waiting
Waiting
Warm · simulated prefill
Waiting
Waiting
Send an inference batch
Current session
Completed
0
Queued
0
Cache hit rate
N/A
Batches wait until their target node has a free GPU replica.
Simplified fleet simulation. Prefix KV stays on the same model and GPU replica.
How does the cache work?
Prompt: With “Reuse prompt prefix” on, requests share a 1,024-token prefix and add 128 fresh tokens. Turn it off for a completely new prompt. A hit requires the same exact prefix, model, and GPU replica.
Storage: Prefix KV stays in that replica’s GPU memory, sharded across its GPUs. KV stored means a node has cached prefixes. In this fleet, nothing transfers between replicas; changing a GPU group’s model configuration clears its KV. This demo retains only the shared prefix between batches.
Reuse: Hits skip the shared prefix’s prefill. Fresh tokens still need prefill; decode still generates an answer. Hit rate = batches with a prefix hit / assigned batches.
Controls: Route pins your batches to a cluster; they wait if it is busy or paused. Click a cluster to pause / resume it. Background demo traffic always routes automatically.
Simple simulation: A dot is an inference batch; 1/2/4/8 GPUs represent model replica sizes. Models are assumed loaded. Exclusive placement, tokens, and timings are illustrative. No real model, continuous batching, memory limits, or memory-pressure eviction.
Engineering
Founding engineer at Vybers, focused on cloud platforms and AI inference infrastructure.
Previously, I worked on Nebula at Epic Systems, building developer tooling and distributed systems.