New branch reason: No prior New Runtime record is supplied for this specific model report, so this begins a distinct record focused on its reported architecture and cache strategy.
Thesis
DeepSeek-V4.1-Flash treats KV-cache footprint and movement as central constraints on long-horizon agent serving, not merely as secondary implementation details.
Observed facts
DeepSeek-AI describes a 552B-parameter multimodal MoE model with context up to one million tokens and a 40-layer Causal Encoder-Decoder split evenly between encoder and decoder layers.
1The report says global KV cache is 890 bytes per token, about one quarter of DeepSeek-V4-Flash, and persistent KV footprint is roughly one eighth with SWA Bounded Replay.
1
Mechanism
Cross-layer KV reuse in Compressed Sparse Attention 2 and FP4 KV caching reduce the global cache, while SWA Bounded Replay reduces persistent cache requirements. The architecture also reports 8B active parameters per token at prefill versus 16B at decode, separating the cost profile of prompt ingestion from generation.
Why now
DeepSeek frames long-horizon agent workloads as increasingly input-heavy, making prefill compute, memory capacity, and cache transfer practical deployment bottlenecks. If these reported reductions hold under real workloads, they could widen the feasible operating envelope for extended agent sessions.
Implications
The first implication is that deployment comparisons for long-context agents should measure cache bytes, persistence, and transfer costs alongside benchmark quality and token pricing.
Reported benchmark scores may attract attention, but independent replication is needed before treating them as comparable evidence of capability.
Evidence boundary
The supplied primary source is DeepSeek-AI’s technical report; its claims and benchmark results are not independently validated by the supplied evidence, and it does not establish production performance or cost.
Watch conditions
The first watch condition is whether released checkpoints and independent evaluations reproduce the cache-footprint and benchmark claims under comparable long-horizon workloads.
Also watch actual serving throughput, latency, and hardware requirements rather than relying on cache size alone.