DecodeAtlas

How frontier models decode

How the major labs spread a model across chips while it writes its answer, as far as anyone has published.

Each column is one of the layouts drawn further down this page. Only the open-weight labs have said how they serve. The closed labs name their chips and little else.

01Four ways to split a model

Every setup on this page is a mix of these four. They differ in what each chip holds and what has to travel between chips.

Colours used throughout: blue weights, gold KV cache (the model's memory of the conversation so far), green experts, red traffic between chips.

02One server, split eight ways

The default in almost every open model card. Eight GPUs share a fast switch, and each holds an eighth of every layer. After each layer they add their partial results together.

03Servers in a line

To fit a model too big for one server, chain servers together, each holding a run of layers. It fits the model but makes no single token faster. The leaked description of GPT-4 (2023) is the only reported layout for any OpenAI model, and it looked like this.

04On TPUs: cut each weight two ways

Google's TPUs are wired as a 3D grid. For its PaLM model, Google published a layout in which every weight matrix is cut along two of the grid's axes, which keeps traffic low as chips are added. How Gemini is laid out has not been published.

05Wide expert parallelism

The big mixture-of-experts models are served on dozens to hundreds of GPUs acting as one. Each GPU handles attention for its own set of users and holds just a few of the experts. In every layer, each token travels to the GPUs holding the experts it needs, and the results travel back.

Each token keeps its home GPU's colour, so you can follow it out to its expert and back. This is how DeepSeek serves its models (144 GPUs per copy in 2025), and how Moonshot's Kimi K2, Meituan's LongCat and Huawei Cloud's deployments work.

06Reading and writing on separate machines

Reading the prompt (prefill) is one big burst of maths. Writing the answer (decode) is one token at a time. Most labs that describe their stack now give the two jobs separate machines and pass the KV cache from one to the other.

Described by DeepSeek, Meta, Moonshot, Meituan, Huawei Cloud and Google (for Gemini).

Some labs split decode itself: attention on one set of machines, experts on another, with batches bouncing between them so neither side waits.

07How many chips make one copy

The chips that work together on a single copy of a model, with the layout each uses. Blue entries are what model cards recommend; gold entries are deployments that labs have described.

08Sources

The long-form report has the detail, a citation for every claim, and where the sources disagree.

  1. DeepSeek, V3/R1 inference system overview
  2. DeepSeek, DeepInfer
  3. Moonshot, Kimi K2 deployment guide
  4. StepFun, Step-3
  5. Meituan, LongCat-Flash
  6. ByteDance, MegaScale-Infer
  7. Huawei Cloud, xDeepServe
  8. Meta, The Llama 3 herd of models
  9. Meta, disaggregated inference at scale
  10. Google, Efficiently scaling transformer inference
  11. Google, serving Gemini at scale
  12. Anthropic, postmortem of three recent issues
  13. The Decoder, the GPT-4 leak
  14. LMSYS, large-scale expert parallelism