II · THE IDEA · ARTIFICIAL INTELLIGENCE
The Bitter Lesson of Compute and Scale
▶ Listen · narrated
When researchers plotted loss against compute, the curves were stubbornly regular. Architecture tweaks looked local; scale looked like the main variable that kept delivering.
At a glance
- Core pattern
- Loss scales as a power law with model size, data and training compute
- Architecture
- Within a wide range, depth-versus-width and similar choices matter weakly
- Sample use
- Larger models are substantially more sample-efficient
- Energy lens
- Training large NLP models carries measurable electricity and carbon cost
- Policy angle
- Calls to report energy use and to consider equitable access to compute
Think of fitting a bigger and bigger engine to the same kind of car, and carefully measuring fuel against speed. The scaling-laws work did something like that for language models: it grew model size, training data and training compute, and watched a standard error measure (cross-entropy loss) fall. The fall was smooth—roughly a straight line on a log-log plot—so doubling resources bought a predictable improvement rather than a mystery leap.
That pattern supports a blunt historical claim. Once a general learning method works at all, pouring in more computation and data often beats inventing a more elaborate special-purpose algorithm. Clever human design still chooses the method, but the big measured gains tracked scale.
The energy paper adds the other side of the metaphor: a bigger engine burns more fuel. Training large NLP models draws a lot of electricity; converted into estimated carbon emissions under stated assumptions, even familiar training runs look costly, and huge automated searches look more costly still. So the lesson has two halves—scale works, and scale is not free.
Kaplan et al. study autoregressive Transformer language models and report that test cross-entropy loss L follows approximate power laws in non-embedding parameter count N, dataset size D, and training compute C over wide ranges (several orders of magnitude). Larger N improves sample efficiency, so the data needed to reach a given loss grows sublinearly with the compute-optimal model size. They discuss compute-optimal allocation: under a fixed FLOPs budget, favour relatively large models, train on enough tokens without assuming convergence on a huge static corpus, and treat many architectural hyperparameters (including depth/width trade-offs inside a broad band) as weak factors compared with N, D and C.
These fits are descriptive trends for the setups measured; they do not by themselves guarantee unbroken exponents at arbitrary scale, and they inherit the tokenisation, optimisation and data mixture of the experiments.
Strubell et al. estimate energy consumption for training and tuning NLP models from hardware power and runtime, then convert to CO₂e with assumed grid intensities. They highlight that reporting only accuracy hides cost, that hyperparameter and neural architecture search can dominate the energy budget relative to a single final training run, and that estimated emissions for aggressive search regimes can reach ranges they compare with long-haul flights or large fractions of passenger-car lifetime emissions, depending on scenario. They recommend energy/carbon reporting and attention to unequal access to compute.
Historically, the two results jointly pressure a research style that seeks ever more specialised algorithms while ignoring resource curves: the measurable path to lower loss has often been general methods plus scale, and the externalities scale with that choice.
Look closer
Three axes, one family of curves
The scaling-laws work treated non-embedding parameter count, dataset size and total training compute as separate levers. On each axis, test loss fell roughly as a power law over a wide range—seven or more orders of magnitude in some plots—rather than as a sudden cliff or a flat plateau. That regularity is what made “just scale it” feel like an empirical programme, not a slogan.
Where human design looked thin
Within broad bounds, many architectural hyperparameters—depth versus width among them—shifted the curves only weakly compared with raw scale. The practical implication was uncomfortable for craft-heavy algorithm design: elaborate inductive structure was easy to over-value relative to more parameters, more data and more optimised steps.
The bill that arrived with scale
A parallel line of work estimated the energy and carbon cost of training common NLP models and of large hyperparameter or architecture searches. Even a single BERT-base training run was placed, in their accounting, in the same rough carbon bracket as a transcontinental passenger flight; fuller search pipelines were far higher. Scale was not free, and the cost was environmental as well as financial.
The story
The bitter lesson, in the sense this lesson needs, is not a moral about bitterness. It is a historical pattern: methods that lean on general learning and ever-cheaper computation have repeatedly outrun methods that encode elaborate human knowledge of the task. In language modelling, that pattern became measurable rather than merely anecdotal when researchers began to treat scale as an object of study in its own right.
Kaplan and colleagues trained families of Transformer language models and asked how cross-entropy loss moved when three quantities changed—model size (non-embedding parameters), dataset size, and the compute used for training. The answers were strikingly regular. Loss improved as power laws in each of those quantities over wide dynamic ranges. The trends did not require a particular clever trick at each new size; they looked like smooth extrapolations. Larger models were also markedly more sample-efficient: they extracted more signal from each token of data than smaller ones did.
Equally important was what mattered less. Over a substantial range, details such as the balance of depth and width did not dominate outcomes the way raw scale did. That finding undercut a familiar research instinct—the hope that a carefully engineered inductive bias would substitute for orders of magnitude in compute. Some bias is still necessary; a model family, an optimiser and a tokenisation scheme are all human choices. But the scaling results suggested that, once a workable general method existed, further gains often came from riding the power laws rather than from stacking on more hand-designed structure.
Those same curves carried an economic reading. If loss is a smooth function of compute, then budgets, not only ideas, set the frontier. Optimal allocation under a compute budget, in their analysis, favoured training quite large models on relatively modest data and stopping short of full convergence on that data—again a prescription about how to spend FLOPs, not about how to encode linguistic theory.
Strubell and colleagues made the other half of the ledger visible. Training modern NLP models consumes substantial energy; when that energy is converted into estimated carbon emissions under stated assumptions about hardware and grids, even routine research practice looks costly. Their estimates placed a single BERT-base training run without hyperparameter tuning in the carbon neighbourhood of a passenger flight across the United States, and placed aggressive neural architecture search far higher—into ranges they compared with multiple long-haul flights or a substantial fraction of a car’s lifetime emissions, depending on the scenario. They argued for reporting energy and carbon alongside accuracy, and for noticing that access to the compute that scaling rewards is unevenly distributed.
Read together, the two lines of work frame a single historical claim. General, compute-heavy learning methods won on the metric the field optimised—held-out loss and the tasks that track it—while the cost of that win shifted onto electricity, carbon and concentration of resources. The lesson is bitter twice over: once for the researchers whose carefully specialised algorithms were overtaken by scale, and once for anyone who assumed that “more compute” was only an engineering detail rather than a policy object.
Why it mattered then
At the turn of the 2020s, language-model results were improving quickly, but it was still easy to tell a story in which each gain came from a new architectural idea. The scaling-laws plots offered a competing story with numbers attached: much of the gain was predictable from size, data and compute alone. That reordered research priorities. It helped justify training larger models, it weakened the prestige of purely hand-crafted structure, and it gave labs a quantitative language for planning budgets. The energy paper arrived in a field that reported parameters and scores far more often than kilowatt-hours. By putting estimated emissions beside familiar model names, it made the research community’s own training practice legible as infrastructure with externalities, not only as clever software. In its moment, that mattered for conference culture, for how groups justified cloud spend, and for early arguments about whether unconstrained search over architectures was scientifically proportional to its cost.
Why it matters now
Power-law thinking still shapes how people plan pre-training runs, compare model families and decide whether a small architectural change is worth a large experiment. The habit of asking “does this beat the scale trend?” is a direct descendant of those curves. At the same time, energy and carbon accounting—however approximate—has become part of responsible-release checklists and procurement debates. The historical pair still frames a live tension: the methods that work best under a loss-versus-compute lens are exactly the methods that press hardest on shared electrical and atmospheric budgets, and on who can afford to participate at the frontier.
The surprising detail
A quiet result in the scaling work is how far one can get while treating architecture as secondary. The same paper that celebrated smooth gains from scale also reported that, inside a wide band, reshaping networks (for example trading depth for width) did little compared with changing parameter count or training compute. The surprise is not that structure never matters; it is how much of the measured progress looked like a resource curve rather than a sequence of conceptual breakthroughs. Pair that with the energy estimates—where a full architecture search could dominate the carbon cost of any single model it produced—and the historical irony sharpens: the search for a cleverer design could cost more environmentally than accepting a simpler design and spending the compute on scale.
What is disputed
Scaling relationships are empirical fits over the model families, tokenisers and ranges studied; they are not proofs that the same exponents continue forever. Energy and carbon figures depend on hardware utilisation, data-centre efficiency and the carbon intensity of the grid assumed in the conversion, so they should be read as scenario estimates, not as universal constants.
Remember this
When loss follows compute, data and size as power laws, general methods that absorb more computation tend to beat intricate human-designed substitutes—and the bill shows up in energy as well as in money.
Test yourself
Suppose two groups reach similar held-out loss. Group A used a simpler model family and spent most of its budget on larger scale; Group B spent a large fraction of its budget on extensive architecture search at smaller scale. Using only the logic of the scaling and energy results, what different questions should you ask about each result before calling it progress?
For Group A, ask where the run sits on the loss-versus-compute and loss-versus-data curves: was the gain the expected power-law return to more resources, and was compute allocated in the regime those laws recommend (large models, enough data, not necessarily training to full convergence)? For Group B, ask what the search cost in energy and carbon under stated hardware and grid assumptions, and whether the winning architecture still beats a simply scaled baseline when that full search budget is counted—not only the final training run. Progress under these papers is not lower loss alone; it is lower loss relative to compute, data and the externalities of obtaining it.
Go deeper
- [1906.02243] Energy and Policy Considerations for Deep Learning in NLP · arxiv.org
- [2001.08361] Scaling Laws for Neural Language Models · arxiv.org
Image: Original diagram, The Daily Triptych. Licence: Original work. Source.