The Architecture Bet: An Asymmetric Encoder-Decoder Beats Brute-Force Scale
V4.1-Flash's 552-billion-parameter mixture-of-experts backbone is deceptively large, but its Causal Encoder-Decoder architecture is what actually does the work: a 20-layer encoder reads the prompt using just 8 billion active parameters, then a separate 20-layer decoder writes the reply using 16 billion active parameters [1]. That is a break from the decoder-only transformer convention most large language models still use, where every token - whether it is being read or written - pays the same per-token compute cost regardless of its role [2]. DeepSeek's framing is direct: 'A 20-layer encoder reads your input using just 8 billion active parameters, then a 20-layer decoder writes the reply using 16 billion' [2].
The architectural split is also what enables the model's aggressive memory footprint reduction. KV cache size compresses to roughly 890 bytes per token, about one-quarter of predecessor V4-Flash's requirement, which cuts HBM needs by roughly 4x and persistent SSD storage needs by roughly 8x [2][5]. Alongside the 552B backbone, DeepSeek added a separate 196-billion-parameter set of sparsely-accessed 'Engram' conditional-memory modules that are consulted only when needed rather than kept fully active [4][5]. Put together, the model is not simply 'bigger' than its predecessor - it is restructured so that most of its parameter count sits in memory-efficient, selectively-activated blocks rather than in dense compute that has to run on every token, which is the underlying reason DeepSeek can offer sustained streaming speeds above 180 tokens per second, with some testers reporting 300 to 400 tokens per second, at a fraction of the usual API cost [2].




