A 671B model only activates ~37B per token: how MoE works and what it costs
techNmak · x · 2026-09-12
A long-form explainer on why a 671B-parameter model doesn't necessarily use 671B parameters for your next token:
- The trick: replace each layer's single feed-forward network with many "expert" subnetworks plus a tiny router that picks which few handle the current token. Specialization is learned, not hand-designed.
- Example: DeepSeek-V3 has 671B total parameters but activates only 37B per token — sparse MoE scales parameter capacity without proportionally scaling compute.
- The overlooked catch: inactive doesn't mean nonexistent. Weights still must be stored across accelerators; routing tokens to the right experts adds communication overhead, and balancing expert utilization is an engineering problem of its own.
- Bottom line: a 671B MoE isn't a secretly small model — it's a 671B model that learned which parts of itself to wake up for each token.
More from Models
- DeepSeek v4.1 Flash runs out of the box on six NVIDIA GPUs via vLLM on day 0, AMD lags — woosuk_k · 2026-09-12
- ARC-AGI cost collapse: DeepSeek-V4-Flash hits 87% at $0.021/task vs o3's $4,500 — inductionheads · 2026-09-12
- Open uncensored AI has demand, but distribution has been stuck for two years — Rumbleblak · 2026-09-12
- DeepSeek V4.1 Flash cuts global KV cache to 890 bytes/token, but HBM demand may rise with agent swarms — teortaxesTex · 2026-09-12
- Claude user complains of contradictory usage limits: unlock time vs 5-hour reset confusion — XCxBigDong69XCx · 2026-09-12
- SGLang hits 873 tok/s on DeepSeek V4.1 Flash within 24 hours of launch — BanghuaZ · 2026-09-12