Paper Breakdowns  /  Chinchilla
Paper 08~7 min readDeepMind · 2022
Paper Breakdown

Chinchilla,
explained.

For years the race was simple: more parameters, bigger model, better AI. Then DeepMind ran the numbers and found the whole field had been building models backwards — too big, and starved of data. Their fix produced a model a quarter the size of the giants that beat all of them.

Video breakdown
The animated walkthrough is in production.
Read the full breakdown below in the meantime ↓
01

The bigger-is-better race

After GPT-3, the headline number was parameter count. 175 billion, then 280 billion (Gopher), then 530 billion. Each lab poured its compute budget into stacking more parameters, on the assumption that size was the lever that mattered most.

But every model is really a bet about how to spend one thing — a fixed compute budget — across two knobs: how many parameters the model has, and how many tokens of data it trains on. The whole field had quietly turned one knob to the maximum and left the other alone.

02

The real question

DeepMind asked it precisely: for a fixed amount of compute, what split between parameters and data gives the best model? To answer, they trained over 400 models across a wide range of sizes and data amounts, and fit curves to how loss falls as you trade one knob against the other.

The answer contradicted the entire industry.

03

The answer: scale both, in lockstep

To use compute optimally, parameters and training tokens should grow together — roughly in equal proportion. Their rule of thumb: about 20 training tokens per parameter. A 10-billion-parameter model wants ~200 billion tokens; double the model, double the data.

By that measure, GPT-3 and Gopher were wildly out of balance — enormous models fed far too little data. They were undertrained: all that parameter capacity sat half-empty because the models never saw enough text to fill it.

Worth knowing

The earlier scaling laws (Kaplan et al., 2020) had suggested most compute should go to parameters. Chinchilla corrected that — its curves put far more weight on data — and it's why post-2022 models are trained on trillions of tokens.

04

The proof: Chinchilla vs Gopher

To settle it, they built Chinchilla: same compute budget as their own 280B Gopher, but spent the compute-optimal way — 70 billion parameters (a quarter the size) trained on 1.4 trillion tokens (about four times the data).

Same compute budget, spent two ways
Gopher
280B params
300B tok
Chinchilla
70B
1.4T tokens
parameterstraining data

Same total compute — just a different split between the two knobs.

05

The numbers

Chinchilla outperformed Gopher, GPT-3, and other far larger models across a broad sweep of benchmarks — language understanding, reasoning, reading comprehension — despite being a fraction of their size.

ModelParametersTraining tokensTokens / param
GPT-3175B~300B~1.7
Gopher280B~300B~1.1
Chinchilla70B1.4T~20

And a deployment bonus falls out for free: a 70B model is far cheaper and faster to run than a 280B one — which matters enormously once millions of people are querying it every day.

06

Why it still matters

Chinchilla rewired how the field spends compute. "Chinchilla-optimal" became standard vocabulary, and the trillion-token training runs behind LLaMA and nearly every capable model since are its direct consequence — smaller, data-rich models tuned for both quality and cheap inference.

It's also a caution against the obvious metric. For years "bigger" was the number everyone chased, and it was the wrong knob to max out. The lesson — balance your budget, don't just crank the one number people brag about — outlasts any single model.

Frequently asked

Quick answers

What is the Chinchilla scaling law?

For a fixed compute budget, the best model scales parameters and training tokens together — roughly 20 tokens per parameter. The compute-optimal frontier is far more data-heavy than pre-2022 practice.

Why were earlier models too big?

GPT-3 and Gopher poured compute into parameters and trained on too few tokens, leaving them undertrained — a smaller model on more data reaches the same or better performance for the same compute.

How did 70B beat 280B?

Chinchilla (70B) used the same compute as Gopher (280B) but trained on ~4x more data (1.4T tokens), following the compute-optimal balance — and won across benchmarks.

What is 20 tokens per parameter?

The paper's rule of thumb for compute-optimal training: about 20 training tokens per model parameter. A heuristic that reframed how teams size models and datasets.

Is bigger always better?

Not for fixed compute. Beyond a point, more parameters without more data wastes compute — and a smaller compute-optimal model is also cheaper and faster to run.

Finished this one? 0 / 30 Paper Breakdowns done

Explore the topic

See this alongside everything else on the same subject — handbooks, system designs, challenges and tools, in one place.

More Paper Breakdowns