Home / Blog / Request pipeline

How a request flows: production system vs OSS DeepInfer

Production numbers below come from DeepSeek’s published inference Q&A / public explainers. They describe the production inference system, not the outcome of installing OSS DeepInfer alone.

Architecture overview

DeepSeek V4.1 Flash inference system architecture overview
Official architecture overview — DeepInfer doc/images/architecture_overview.png (Apache-2.0)

Request path (conceptual)

StepComponentWhat happensIn OSS?
1API / recipeMessages · Chat Completions · Responses → Conversation → tokensrecipe is separate MIT repo
2Entrypoint / cache matchPrefix / KV hit length before routingKV store not OSS
3Prefill engineCompute non-cached suffix; write KVengine yes; service glue no
4Decode engineAutoregressive tokens; Wide-EP MoEengine yes; LB/disagg no
5Sampler / DSparkDraft + confidence-scheduled verifyflags in README
6recipe parseToken stream → protocol events (reasoning / tools / text)recipe yes

Production snapshot (attribution required)

MetricReported valueLabel
Cluster tokens/day~155 trillionProduction system
Valley revenue~US$38 / GPU-hourProduction system
Avg input · cache hit~77K · ~96%Production system
TTFT~400 ms avgProduction system
Prefill no-cache → cache~60k → ~1.5M tok/s/GPU (~25×)Production system
Decode · user speed~14k tok/s/GPU · ~230 tok/s (~300 code)Production system
Efficient unit~64P + 64D · P:D ≈ 1:1Production / Q&A

OSS gap callout

Continue: install · hardware · vs vLLM · recipe · FAQ.