Skip to main content

LLM Construction

Scaling Compute-Optimal Training

Chinchilla scaling: how to optimally allocate a fixed compute budget between model size and training data, why many models were undertrained, and the post-Chinchilla reality of data quality and inference cost.

AdvancedTier 2FrontierSupporting~55 min

Prerequisites

Learning position

Place this page in a reading path.

llm-construction | layer 5 | tier 2. This page has 1 direct prerequisite and 0 published dependents.

What next

Take the diagnostic

No published continuation is declared yet, so the diagnostic is the clean next route.

Evidence badge

Source-grounded page

This page has no public Lean mapping yet. Use the evidence page to inspect how claim status labels work.

Show the backing system

Why This Matters

Training a large language model costs millions of dollars. The question of how to spend that compute budget is not academic. Chinchilla (Hoffmann et al., 2022) showed that many existing models, including Gopher (280B parameters), were significantly undertrained: they used too many parameters relative to the amount of training data. The practical consequence was that a smaller, properly trained model (Chinchilla, 70B) outperformed a larger undertrained one (Gopher, 280B) while using the same total compute.

Hide overviewShow overview
Five-panel infographic on scaling and compute-optimal training: training compute as parameters x tokens (FLOPs ~ 6 N P), undertrained vs compute-optimal vs over-trained regimes (Chinchilla framing), scaling-law intuition with the Chinchilla-style optimal frontier and 'loss = a + b/C^c', practical budget tradeoffs (compute, wall-clock, GPU memory, dataset quality), and why this matters (frontier training, smaller efficient models, fine-tuning strategy, research planning).
Scaling works best when model size and data scale together under a fixed compute budget. Otherwise you waste computation on a model that is too large or too data-starved.

This reshaped how labs allocate training budgets and shifted attention toward data quality, data efficiency, and the previously underappreciated cost of inference.

Background: Kaplan Scaling

Kaplan et al. (2020) established power-law relationships between loss LL and three quantities: parameters NN, data DD, and compute CC.

Definition

Kaplan Scaling Laws

For a fixed architecture (decoder-only transformer), cross-entropy loss on held-out data follows:

L(N)≈αN⋅N−0.076L(N) \approx \alpha_N \cdot N^{-0.076} L(D)≈αD⋅D−0.095L(D) \approx \alpha_D \cdot D^{-0.095} L(C)≈αC⋅C−0.050L(C) \approx \alpha_C \cdot C^{-0.050}

where the exponents are fit empirically. Kaplan concluded that loss is more sensitive to NN than to DD: you should scale parameters faster than data.

The Kaplan recommendation: for a 10x increase in compute, increase NN by 5.5x and DD by 1.8x. This led to the trend of building very large models trained on relatively little data (e.g., GPT-3 at 175B parameters trained on 300B tokens).

Chinchilla Optimal Allocation

Proposition

Chinchilla Compute-Optimal Allocation

Statement

For a fixed compute budget CC, the loss-minimizing allocation scales parameters and data roughly equally:

Nopt∝C0.50,Dopt∝C0.50N_{\text{opt}} \propto C^{0.50}, \quad D_{\text{opt}} \propto C^{0.50}

Equivalently, the optimal token-to-parameter ratio is approximately D/N≈20D/N \approx 20. A model with NN parameters should be trained on roughly 20N20N tokens.

Intuition

If you have NN parameters and very little data, you overfit. If you have vast data but a tiny model, you underfit. The optimal point balances these two sources of error. Chinchilla found this balance is roughly equal scaling, not the parameter-heavy allocation Kaplan suggested.

Proof Sketch

Model the loss as L(N,D)=E+A/Nα+B/DβL(N, D) = E + A/N^\alpha + B/D^\beta where EE is irreducible loss. Using C≈6NDC \approx 6ND, substitute D=C/(6N)D = C/(6N) and minimize over NN. Setting dL/dN=0dL/dN = 0 gives Nopt∝Cβ/(α+β)N_{\text{opt}} \propto C^{\beta/(\alpha + \beta)}. Chinchilla found α≈β≈0.34\alpha \approx \beta \approx 0.34, giving exponent ≈0.50\approx 0.50 for both NN and DD.

Why It Matters

This directly changed how labs train models. GPT-3 (175B, 300B tokens) had a tokens-per-parameter ratio of about 1.7, far below the Chinchilla-optimal 20. Llama 1 (65B, 1.4T tokens) and Llama 2 (70B, 2T tokens) adopted Chinchilla-like ratios. The result: smaller models that perform as well as or better than larger undertrained models, at lower inference cost.

Failure Mode

The Chinchilla result assumes that all tokens are equally valuable and that data is abundant. In practice, high-quality text data is finite. When you run out of quality data, the model cannot absorb more tokens effectively. This shifts the problem from "how many tokens" to "which tokens."

Kaplan vs Chinchilla

Proposition

Kaplan vs Chinchilla Exponent Discrepancy

Statement

Kaplan found optimal allocation exponents of N∝C0.73N \propto C^{0.73} and D∝C0.27D \propto C^{0.27}, favoring parameters over data. Chinchilla found N∝C0.50N \propto C^{0.50} and D∝C0.50D \propto C^{0.50}, favoring equal allocation. The discrepancy comes from differences in experimental methodology.

Intuition

Kaplan's experiments did not train each model to convergence. Models with more parameters appeared to improve loss more per FLOP because they had not yet reached their optimal loss for that amount of data. Chinchilla trained each model fully, revealing that data had been undervalued.

Proof Sketch

Not a formal proof. The key methodological differences: (1) Kaplan used a fixed number of training steps for models of different sizes; Chinchilla varied both model size and training duration. (2) Kaplan used a fixed learning rate schedule; Chinchilla tuned the schedule per run. (3) Chinchilla used three independent estimation approaches (fixed NN varying DD, IsoFLOP profiles, and parametric loss fitting) that agreed on the equal-scaling result.

Why It Matters

This is a cautionary tale about empirical scaling research. Both groups fit power laws to real data and reached different conclusions because of experimental design choices. The lesson: scaling law exponents are not universal constants. They depend on the training protocol, architecture, and data distribution.

Failure Mode

Neither Kaplan nor Chinchilla accounts for data quality. A model trained on 20N tokens of noisy web scrapes may perform worse than one trained on 5N tokens of curated text. The Chinchilla ratio of 20 tokens per parameter is a rough guideline, not a physical law.

Post-Chinchilla Reality

Data quality dominates data quantity. Llama 3 (2024) trained on 15T tokens for a 70B model (ratio: ~214 tokens per parameter), far exceeding the Chinchilla-optimal 20. This works because the data was heavily filtered and deduplicated. The Chinchilla analysis assumed constant data quality; real training benefits from spending more compute on better data even past the "optimal" ratio.

Inference cost matters. Chinchilla minimizes training loss per training FLOP. But a model is trained once and served many times. A 70B model costs roughly 4x more per token to serve than a 20B model. If your total lifetime cost is dominated by inference (which it usually is at scale), you may prefer a smaller model trained longer, even if it uses more training FLOPs than Chinchilla-optimal. This is sometimes called "inference-aware scaling."

Overtraining is common and deliberate. Llama models are deliberately "overtrained" relative to Chinchilla: more tokens per parameter than the compute-optimal ratio. This increases training cost but yields a smaller model that is cheaper to serve. The trade-off is rational when inference volume is high.

Repeating data degrades performance. Muennighoff et al. (2023) showed that repeating training data (training for more epochs) gives diminishing returns after about 4 epochs, and performance can degrade. This creates a hard constraint: if you run out of unique high-quality data, more compute does not help much.

Common Confusions

Watch Out

Chinchilla optimal does not mean actually optimal

Chinchilla-optimal minimizes loss for a given training compute budget. It does not account for inference cost, data quality variation, or the finite supply of training data. A model that is "Chinchilla-optimal" may be suboptimal for actual deployment.

Watch Out

Scaling laws predict loss, not capability

A 0.01 nats improvement in cross-entropy loss can flip a model across a qualitative capability (like arithmetic) or might have no noticeable effect on downstream tasks. Scaling laws describe smooth loss curves, but capabilities can emerge discontinuously (though the sharpness of emergence is debated).

Exercises

ExerciseCore

Problem

You have a compute budget of C=6×1021C = 6 \times 10^{21} FLOPs and use the approximation C≈6NDC \approx 6ND. Using the Chinchilla-optimal ratio D/N≈20D/N \approx 20, compute the optimal model size NN and number of training tokens DD.

ExerciseAdvanced

Problem

Suppose inference costs cIc_I per token and you will serve TinfT_{\text{inf}} total inference tokens over the model's lifetime. Training costs cT⋅C=cT⋅6NDc_T \cdot C = c_T \cdot 6ND total. The total cost is cT⋅6ND+cI⋅N⋅Tinfc_T \cdot 6ND + c_I \cdot N \cdot T_{\text{inf}} (where inference cost scales linearly with NN). For fixed target loss L∗L^*, how does the optimal NN change compared to pure Chinchilla-optimal?

Related Comparisons

References

Canonical:

  • Hoffmann et al., "Training Compute-Optimal Large Language Models" (NeurIPS 2022)
  • Kaplan et al., "Scaling Laws for Neural Language Models" (2020)

Current:

  • Touvron et al., "Llama 2: Open Foundation and Fine-Tuned Chat Models" (2023)
  • Muennighoff et al., "Scaling Data-Constrained Language Models" (NeurIPS 2023)
  • Sardana, Portes, Doubov & Frankle, "Beyond Chinchilla-Optimal: Accounting for Inference in Language Model Scaling Laws" (arXiv:2401.00448, 2024) -- formalizes the inference-aware scaling argument used implicitly by the Llama overtraining recipe
  • Besiroglu et al., "Chinchilla Scaling: A Replication Attempt" (arXiv:2404.10102, 2024) -- replication of Hoffmann et al. recovers α≈0.35\alpha \approx 0.35 but flags reporting errors in the original loss-fit table
  • Schaeffer, Miranda, Koyejo, "Are Emergent Abilities of Large Language Models a Mirage?" (NeurIPS 2023) -- argues many "emergent" capabilities are artifacts of discontinuous metrics; relevant to the loss-vs-capability confusion above
  • Krajewski et al., "Scaling Laws for Fine-Grained Mixture of Experts" (ICML 2024) -- joint (N,D,E)(N, D, E) scaling law for MoE that subsumes Chinchilla as the dense E=1E=1 limit

Foundational context:

  • Sutton, "The Bitter Lesson" (2019) -- the methodological backdrop for why scaling-law work matters at all

Last reviewed: May 27, 2026

Cite this page

Sneiderman, Robby. "Scaling Compute-Optimal Training." TheoremPath, reviewed 2026-05-27. https://theorempath.com/topics/scaling-compute-optimal-training

Canonical URL
https://theorempath.com/topics/scaling-compute-optimal-training
Author
Robby Sneiderman, TheoremPath
Last reviewed
2026-05-27
What this is
A reference page on TheoremPath. Written and maintained by the named author. Not peer reviewed and not refereed by any venue. Each claim below carries its own verification status.
Terms
All rights reserved. Non-commercial quotation with attribution permitted.

Citing one claim

2 statements on this page are separately addressable. Each carries an identifier of the form claim:<topic>::<statement> printed beside it, and resolves to that identifier's anchor on this URL. Quote the statement, its assumptions, and its failure modes together.

Recorded verification on this page: 2 informal_only.

  • This page is a secondary source. Where a claim cites literature, the result is due to that source and not to this site.
  • 2 of 2 claims on this page name no source. Their attribution to the literature is not recorded here, whatever their verification status says.
  • 2 of 2 carry neither a source nor a proof check. Their provenance is the author's reading of the literature; check them against a primary source before relying on them.
  • Statements are given in LaTeX exactly as authored. The rendered page passes the same LaTeX through KaTeX, so text scraped from the HTML repeats expressions and drops radicals; quote from statementTex.

/claims.json lists 1,178 of the 1,231 statements this site records, with the anchor and the recorded verification of each. What earns a place in it: a theorem, lemma, corollary, or proposition block on a published topic page. Definitions are not listed, and neither are the 27 statements on comparison pages. A missing entry means the rule above did not select the statement, not that this site is silent on the result.

Canonical graph

Required before and derived from this topic

These links come from prerequisite edges in the curriculum graph. Editorial suggestions are shown here only when the target page also cites this page as a prerequisite.

Required prerequisites

1

Derived topics

0

No published topic currently declares this as a prerequisite.