Scale and scaling laws
How loss falls as a power law in parameters, data, and compute — and how labs plan trainings with that math.
The most consequential empirical discovery of the LLM era is that pretraining loss falls as a smooth power law in three variables: parameters , data , and compute . Not in jumps, not chaotically — predictably, across six-to-seven orders of magnitude. This lesson is about what that buys and how to spend it.
Start here
Scaling laws turned model training into an engineering discipline: measure the curve on cheap small runs, extrapolate, then commit billions of compute to the big run with the outcome largely known in advance.
The law
In log-log space, the relationship is nearly a straight line:
with exponents in the tens-of-percent range — every 10× of parameters buys a predictable chunk of loss reduction, even when the improvement looks invisible step to step. Two landmark results:
- Kaplan et al. (2020) — loss follows clean power laws in , , and ; bigger models are more sample-efficient (they need less data per parameter to reach the same loss).
- Hoffmann et al., "Chinchilla" (2022) — at a fixed compute budget, the best loss comes from scaling parameters and data together, roughly 20 tokens of data per parameter. The field had been over-investing in parameters and under-training them.
Spending a budget wisely
The Chinchilla insight is easiest to see as a budget problem: every training run spends compute as roughly . For one fixed budget, you can buy a big under-fed model or a smaller well-fed one — the loss surface picks the sweet spot:
One compute budget, many ways to spend it (params N × tokens D)
Sweet spot at N ≈ 16 params, D ≈ 0k tokens (loss 2.82) — Chinchilla's finding: at a fixed budget, model size and data should grow *together*. (The real fit lands near 20 tokens per parameter; the toy's ratio differs but drifts only within a narrow band as the budget scales.)
Synthetic power-law surface for illustration — real papers fit these curves on thousands of runs, and labs use them to plan billion-dollar trainings before starting.
Move the budget slider and the optimum shifts — but its tokens per parameter stays in a narrow band. That stability is the practical takeaway labs distilled into planning tools (in the real fit, the band centers near 20 tokens per parameter).
Note
Frontier labs fit these curves with hundreds of small proxy runs, then use the fitted law to choose the final model's size, data, and training duration. GPT-4-class trainings are planned on paper like this before a single large run starts — scale is computed, not guessed.
Emergence: the discontinuous surprise
The smooth law hides a stranger phenomenon: some abilities — multi-step arithmetic, following multi-part instructions — appear near nonexistent at smaller scale and jump sharply past a threshold. The practical reading: scaling buys qualitative new behavior, not just quantitative refinement.
But hold the claim at arm's length — the debate it triggered is instructive. Schaeffer et al. (2023) showed many "emergent" abilities measure exactly what you'd predict from a smooth underlying curve viewed through a discontinuous metric: on exact-match scoring (all digits right or zero credit), a model improving steadily per-digit still scores 0% until the last digit comes online — the jump is in the ruler, not necessarily the capability. Switch to a smooth metric (partial credit, per-token likelihood of the right answer) and most "emergences" decompose into gradual gains.
The honest split to carry:
- Per-token loss is smooth in every regime measured directly. Data-constrained regimes (heavy epoch reuse) require amendments the original law didn't anticipate, but the smooth shape holds.
- Task-level metrics can jump — partly real (some abilities do require integrated multi-step competence, and partial-credit progress doesn't help a user who needs the whole chain), partly metric artifact. "Emergence" is partly physics, partly how we graded the exam.
The practical consequence survived the debate either way: small proxy models do not reliably tell you which tasks a big model will do well — they tell you the loss. Planning capability (not just loss) needs task-level evaluation at multiple scales.
Scale's side-effects
Scaling is not free capability:
- Costs concentrate — a frontier training run is months of an entire GPU cluster; the loss curve must be trusted before launch.
- Inference inherits the size — a bigger model is slower and costlier to serve forever, which is why efficiency tricks (next lesson) and distillation matter commercially.
- Data becomes the binding constraint — Chinchilla-optimal training of a 1T-parameter model would need more tokens than exist in publicly crawlable text. Quality, synthetic data, and reuse (more epochs than Chinchilla assumed) are the modern adaptations.
Next: the tricks that make big models cheap to build and serve — FlashAttention, mixed precision, and friends.