Table of Contents
In December 2024, Chinese AI company DeepSeek published a technical report that made a lot of people in the AI research community run the numbers twice: they trained a 671B-parameter model using 2.78 million H800 GPU-hours at a cost of approximately $5.57 million. By comparison, GPT-4’s training cost is estimated to exceed $100 million. Comparable performance, roughly one-twentieth the training cost, fully open source. The implications go beyond “cheap AI” — this was a fundamental recalibration of the industry’s assumptions about training efficiency.
TL;DR
DeepSeek V3 is a 671B total-parameter MoE (Mixture of Experts) model that activates only 37B parameters per token. Through innovations including MLA (Multi-head Latent Attention), auxiliary-loss-free load balancing, and multi-token prediction, it was trained in 2.788M H800 GPU-hours at approximately $5.576M. It matches or approaches top closed-source models on multiple benchmarks. API pricing is approximately $0.028 per million input tokens — one-tenth the cost of OpenAI’s equivalent-scale models.
Design Philosophy
DeepSeek’s core question was: where is the efficiency ceiling for AI training?
The mainstream view held that frontier models require massive GPU clusters and astronomical budgets. OpenAI, Google, and Anthropic’s training costs doubled with each generation. DeepSeek took the opposite approach — asking “what can architecture design achieve within a fixed compute budget?”
This thinking shows up in several concrete decisions:
- Choose MoE over dense: MoE gives you large parameter count (strong expressiveness) without activating everything during inference (less compute)
- Optimize for hardware available in China: The H800 is the export-controlled version of the H100, with lower memory bandwidth. DeepSeek had to optimize cross-node communication under this constraint
- Co-design algorithms, framework, and hardware: Rather than assuming the best hardware, squeeze maximum efficiency from existing conditions
Core Concepts
MoE Architecture
In DeepSeek V3’s Transformer architecture, FFN (feed-forward network) layers are replaced with MoE layers. Each MoE layer has 256 expert modules, and each token is routed to 8 of them. Out of 671B total parameters, only ~37B activate per forward pass — making inference compute similar to a 37B dense model while retaining the model capacity of 671B.
DeepSeekMoE improvements:
- Added “shared experts” on top of standard MoE, ensuring certain common knowledge isn’t routing-dependent
- Fine-grained experts (256 instead of the traditional 8–16), allowing more precise routing
Multi-head Latent Attention (MLA)
Traditional MHA (Multi-head Attention) KV Cache consumes large amounts of memory for long text. MLA’s innovation is projecting K and V into a low-dimensional latent space before expanding them — dramatically reducing KV Cache memory footprint and memory bandwidth requirements during inference.
This matters especially when running long-context inference on memory-bandwidth-limited H800s.
Auxiliary-Loss-Free Load Balancing
A classic MoE problem is expert collapse — the router tends to send all tokens to a few experts, leaving most experts undertrained. The traditional fix is adding auxiliary loss functions to penalize imbalance, but this interferes with the primary training objective.
DeepSeek V3’s solution adds token-level bias terms before the softmax routing, dynamically adjusted without extra loss functions. Load balancing is equally effective without affecting the model’s main task learning.
Multi-Token Prediction
Traditional language models predict one next token at a time. DeepSeek V3 introduces multi-token prediction (predicting the next N tokens), letting the model learn longer-range dependencies during training and increasing training signal density.
Comparison with Alternatives
| Model | Type | Active Params | Training Cost (est.) | Open Source | API per 1M input tokens |
|---|---|---|---|---|---|
| DeepSeek V3 | MoE | 37B | ~$5.6M | Yes | $0.028 |
| GPT-4 | Dense (est.) | ~1T | >$100M | No | $10 |
| Claude 3.5 Sonnet | Undisclosed | Undisclosed | Undisclosed | No | $3 |
| Llama 3.1 405B | Dense | 405B | >$30M (est.) | Yes (partial) | Provider-dependent |
| Mistral Large | Dense | 123B | Undisclosed | No | $3 |
DeepSeek V3’s pricing is approximately 107x cheaper than Claude Sonnet and 357x cheaper than GPT-4 — making large-scale deployment cost structures look completely different.
When to Use It (and When Not To)
Good fit:
- Commercial applications making high volumes of API calls (cost advantage most pronounced)
- Code generation, mathematical reasoning, long-form text (V3’s strengths)
- Local deployment with limited compute (MoE inference compute is close to a 37B dense model)
- Research purposes (full technical report and model weights available)
Not a good fit:
- Applications requiring the strictest data privacy (model from a Chinese company, API deployed on Chinese servers)
- Real-time voice interaction (not a speed strength for inference)
- Medical or legal applications requiring maximum accuracy (gap vs. GPT-4 o1/o3 reasoning capability)
The Big Picture
DeepSeek V3 changed the cost reference point for AI training. It’s not saying “billion-dollar systems have no value” — it’s saying “certain performance levels don’t require billions.”
The industry impact is already visible: OpenAI, Anthropic, and Google all accelerated their cheaper model offerings, and API pricing dropped continuously through 2025. DeepSeek’s contribution isn’t just a good model — it’s the complete open publication of MoE efficiency optimization research, giving the whole community a foundation to build on.
DeepSeek V4’s technical preview was released in April 2026, and is worth watching.
References
Answers come from this article only. Click any prompt below or open the chat at the bottom right.
🇺🇸 English
In December 2024, a Chinese AI company called DeepSeek published a technical report that made a lot of people in the research community stop and run the numbers a second time. They trained a model with 671 billion parameters, and they did it using about 2.78 million H800 GPU-hours, at a cost of roughly 5.6 million dollars. Now hold that number next to GPT-4, whose training cost is estimated at over 100 million dollars. So you're looking at comparable performance, at somewhere around one-twentieth the training cost, and the whole thing is fully open source. And here's why that matters: this wasn't just "cheap AI." This was a fundamental recalibration of what the entire industry had been assuming about how expensive it takes to train a frontier model.
Let me give you the quick shape of it. DeepSeek V3 is what's called a Mixture of Experts model. It has 671 billion parameters in total, but — and this is the clever part — it only activates about 37 billion of them for any given token. Through a handful of architectural innovations, which we'll walk through, they got the training done for about 5.6 million dollars, and it matches or comes close to the top closed-source models on a range of benchmarks. And the API price? Roughly one-tenth of what OpenAI charges for a comparable model.
So let's talk about the philosophy behind this, because it's genuinely interesting. The core question DeepSeek asked was: where is the efficiency ceiling for AI training? The mainstream belief at the time was that if you want a frontier model, you need a massive GPU cluster and an astronomical budget. OpenAI, Google, Anthropic — their training costs were roughly doubling every generation. DeepSeek flipped the question around. Instead of "how much compute can we throw at this," they asked, "within a fixed compute budget, how far can smart architecture design take us?"
And that mindset shows up in three concrete choices. First, they went with Mixture of Experts instead of a dense model, because that gives you a huge parameter count — which means the model is very expressive — without having to fire up every parameter during inference. Second, they optimized specifically for the hardware they could actually get in China. The H800 is the export-restricted cousin of the H100, and it has lower memory bandwidth, so they had to get very clever about how chips talk to each other across nodes. And third, they co-designed the algorithm, the software framework, and the hardware all together, rather than just assuming they'd have the best chips on the planet.
Now let's get into the actual machinery, because there are four ideas worth understanding.
The first is that Mixture of Experts architecture. In a normal Transformer, you've got these feed-forward layers. DeepSeek replaced them with MoE layers. Picture each MoE layer as having 256 little specialist modules — the "experts." When a token comes through, a router picks just 8 of those 256 experts to handle it. So out of 671 billion total parameters, only about 37 billion light up on any single pass. The result is that inference costs about as much compute as a 37-billion-parameter model would, but you still get the knowledge and capacity of a 671-billion-parameter model. DeepSeek also added a twist: alongside those specialist experts, they included "shared experts" that every token passes through, so common, general knowledge doesn't depend on the router's decisions. And they made the experts fine-grained — 256 of them instead of the traditional 8 to 16 — which lets the routing be much more precise.
The second idea is Multi-head Latent Attention, or MLA. Here's the problem it solves. When a model processes long text, it has to keep something called a KV cache in memory, and traditional attention makes that cache balloon — it eats memory. MLA's trick is to squeeze the keys and values down into a compact, low-dimensional space before expanding them back out when needed. That dramatically shrinks how much memory the cache takes and how much memory bandwidth you need. And remember — those H800 chips are bandwidth-limited, so this is exactly the kind of optimization that pays off big when you're running long-context inference on that hardware.
The third idea tackles a classic headache with Mixture of Experts, something people call expert collapse. The router has a bad habit of funneling almost everything to a handful of favorite experts, which means the rest of them never get properly trained. The usual fix is to bolt on an extra penalty — an auxiliary loss — that punishes imbalance. But that penalty fights against the main thing you're trying to teach the model. DeepSeek's answer was elegant: they add a small bias term to each expert before the routing decision, and they nudge those biases dynamically to keep the load balanced. No extra loss function, no interference with the model's real learning. You get balanced experts for free, basically.
And the fourth idea is multi-token prediction. Normally a language model predicts one next word at a time. DeepSeek V3 trains the model to predict several upcoming tokens at once. That pushes the model to learn longer-range dependencies and it packs more learning signal into every training step.
Okay, so how does this stack up against the competition? Let me paint the comparison for you. DeepSeek V3 activates 37 billion parameters, cost about 5.6 million dollars to train, it's open source, and its API runs around three cents per million input tokens. GPT-4, by contrast, is a dense model estimated at around a trillion parameters, cost north of 100 million dollars to train, is closed, and charges about 10 dollars per million input tokens. Claude 3.5 Sonnet keeps its size and cost private, closed source, priced at 3 dollars. Llama 3.1 405B is a dense 405-billion-parameter model, cost an estimated 30 million-plus, partially open. And Mistral Large is a dense 123-billion model, closed, also around 3 dollars.
Let those price gaps sink in. DeepSeek V3 is roughly 107 times cheaper than Claude Sonnet and about 357 times cheaper than GPT-4. When your per-call cost drops by two orders of magnitude, the entire economics of deploying AI at scale looks like a completely different game.
So when should you actually reach for this thing? It's a great fit if you're running a commercial application making huge volumes of API calls — that's where the cost advantage really screams. It's strong at code generation, mathematical reasoning, and long-form text. It's good for local deployment when your compute is limited, because remember, its inference cost behaves like a much smaller 37-billion model. And it's excellent for research, since the full technical report and the model weights are right there for you.
But it's not for everything. If you need the strictest data privacy, keep in mind this is a model from a Chinese company with an API hosted on Chinese servers. If you're building real-time voice interaction, raw inference speed isn't its standout strength. And for the highest-stakes accuracy work — medical or legal reasoning where you want every last bit of correctness — there's still a gap between this and the top-tier reasoning models like GPT-4's o1 and o3.
So let's zoom out to the big picture. What DeepSeek V3 really did was move the cost reference point for the whole industry. It's not claiming that billion-dollar systems are worthless — it's making a sharper point, which is that reaching a certain level of performance simply doesn't require billions. And you can already see the ripple effects: OpenAI, Anthropic, and Google all sped up their cheaper model offerings, and API prices kept sliding downward through 2025. But maybe the biggest gift here isn't the model itself — it's that DeepSeek published the complete recipe for MoE efficiency, out in the open, giving the whole community a foundation to build on. And there's a sequel coming: DeepSeek V4's technical preview landed in April 2026, and it's well worth keeping an eye on.
So let me leave you with the three things to remember. First, the headline: DeepSeek proved you could reach near-frontier performance for around 5.6 million dollars instead of 100 million-plus — a twentyfold cut in training cost. Second, that didn't happen by accident; it came from stacking smart architecture on top of hardware constraints — Mixture of Experts to keep active compute small, Latent Attention to tame memory, a loss-free trick to balance the experts, and multi-token prediction to squeeze more out of every training step. And third, the lasting impact isn't really about one model — it's that by open-sourcing the whole efficiency playbook, DeepSeek reset the industry's assumptions and dragged everyone's prices down with it. Cheaper wasn't the point. Rethinking what "expensive" even means — that was the point.
🇹🇼 中文
DeepSeek 4 發布了,隨附一篇 58 頁的研究論文,而且這次幾乎沒藏私。它是目前我們能免費使用的最大型開源 AI 模型之一,而最搶眼的數字只有一個:一百萬 token 的 context window,而且是開源權重。
換成人話,你可以一次餵給它大約一千五百頁的密集技術文件,它全部讀進去。這種等級的長 context,兩年前還是 Google Gemini 拿來震撼全場的招牌,現在卻以開源、免費的形式,直接送到我們手上。
它分成兩個版本。Pro,效果大致追平幾個月前那些數十億美元等級的前沿模型;Flash 體積小很多,卻在某些場景下能跟 Pro 較勁。更誇張的是算力——隨著輸出越來越長,新的 Pro 版本比上一代大約省下三倍算力,輕量的 Flash 甚至省下十倍。同樣的能力,用更少的計算就跑得出來。
那真正的魔法在哪?在於它怎麼處理 KV cache。你可以把 KV cache 想成模型在推論時的草稿紙——你寫進去的 prompt、塞進去的文件,都存在這裡。context 越長,草稿紙越大,記憶體很快就撐不住。DeepSeek 4 用三層壓縮來解,我用「讀一本書」來比喻。
第一層,是 token 層級的壓縮,也就是摘要。就像讀書時把每一段濃縮成一句話,書還在,但你搜尋起來快多了。
第二層,叫 Heavily Compressed Attention,管的是結構。光有摘要還是會累積成一大坨。你想知道整本書的大致劇情?看目錄就好,每章一個短名字,一眼掌握全局。論文說這一層是一百二十八比一的壓縮。
第三層,Compressed Sparse Attention,管的是索引。目錄還不夠精準。你想找書裡某一場打鬥發生在哪一頁?翻索引——一份「詞彙到位置」的清單,直接把你帶到最相關的那幾頁。
三層疊起來——摘要、結構、索引——把 KV cache 的記憶體需求砍掉大約九成。等於把一百個字塞進十個字的空間,而論文宣稱資訊幾乎沒有損失。這裡有個重要釐清:壓縮的是 KV cache,不是模型本身。你還是得把完整模型載入進來,別被媒體標題騙成「可以把整個 DeepSeek Pro 塞進一台烤麵包機」——那是兩回事。
壓得這麼狠,會不會把資訊壓丟?作者用了經典的長文本記憶測試:在越來越長的 context 裡藏進八個事實,看模型能不能全部找回來。結果是,Pro 版本的回想表現,比 Google 旗艦 Gemini 3.1 Pro 還好。這對一個開源免費模型來說,相當驚人。不過講句公道話——就跟其他系統一樣,你越接近 context window 的上限,模型就開始退化:遺忘、飄移、幻覺。文字塞得越滿,真實度越低,這條界線要留意。
寫程式這塊它很強,你可以輕鬆請它產一段 JavaScript,貼到網頁就能跑,某些情況甚至能在 DeepSeek 的視窗裡一鍵執行。但它不是萬能。作者本身做 light transport,也就是 ray tracing 研究,拿相關的小題目去試,一般任務沒問題,但碰到比較進階的演算法,它仍然無法正確實作。強,但有天花板。
價格呢?如果你自架,硬體不便宜;但官方也提供線上存取,而且便宜到數字快失去意義——有折扣的時候,大約比 Anthropic 的 Claude 便宜三十倍;沒折扣,也便宜八到二十倍。
但有三個限制媒體標題通常不會提。第一,它只支援文字,不是多模態。它能吞一千五百頁文件,卻不能吃十小時音訊或一整部電影,沒圖片、沒音訊,用作者的話說就是「又瞎又聾」。第二,連作者自己都沒完全搞懂——論文提到有兩個技巧能神奇地穩定訓練,但他們坦承不太確定為什麼有效,這份透明度反而值得尊重。第三,逼近 context 上限就會崩,越往窗口邊緣推,表現越不穩。
論文還順帶用到一個叫 Engram 的技術。一般的 AI 幾乎每次都要把每個事實從頭重算一遍;Engram 讓它可以直接「回想」已經算過的事實,而不是重算。聽起來簡單,實作沒那麼容易。
最後我想把它的核心思路,借來用在思考上。想像你在森林裡散步,你想抬頭看眼前的美景,可一抬頭就可能絆倒;於是你只好盯著腳前的路。看風景,還是看腳步,你沒辦法同時做。解法是什麼?兩件都做——近處掃一眼,遠處瞄一眼,一步一看,局部細節配上全局脈絡。而這,正是 DeepSeek 4 在做的事。
所以收尾我留三個重點。第一,它最大的突破是三層 KV cache 壓縮,把記憶體砍掉約九成,才把一百萬 token 塞進開源模型。第二,長文本記憶它贏過 Gemini 3.1 Pro,價格還便宜到誇張,但代價是純文字、逼近上限會崩。第三,「近掃、遠望」不只是模型的招——同時抓住細節與全貌,也是我們自己可以練的思考方式。
Tags
Related Articles
RAG's Five Stages: From Pipeline to Reasoning Retrieval, and the Naive RAG on My Own Site
Over the past two years RAG evolved from a 'linear pipeline' to 'loop-based reasoning'. It maps cleanly to five stages: Naive, Advanced, Modular, Graph, Agentic. The real inflection point is control moving from pipeline to agent — a System 1 → System 2 shift. Looking back at engineer-news's own RAG stack, it's stuck at the Naive edge — so this post also lays out what to fix next.
Building a Real RAG: 5 Infra Lessons from InfiniFlow's 2024 Year-in-Review
The previous post zoomed out for a five-stage panorama of RAG. This one zooms in on the five infra lessons any real RAG has to face: document ingestion, contextualized chunking, three-lane hybrid search, tensor reranker, and GraphRAG's semantic gap. Each lesson is checked against engineer-news's current stack, ending with a priority list for a personal site.
J-lens: Anthropic's New Interpretability Tool for Reading Claude's Inner Thoughts via a 'Global Workspace'
Anthropic proposes J-lens, an interpretability tool that captures the 'verbalizable' representations inside a Transformer, and uses it to show that Claude contains a privileged subspace analogous to the neuroscientific 'global workspace' — a small set of vectors that broadcast, drive reasoning, respond to external steering, and even leak signals during deception and evaluation awareness.