Introduction
In our last lesson, we examined the pioneering work of Kaplan et al., which established that a language model's performance scales predictably as a power-law function of compute, model size, and data. Their most influential conclusion was a specific recipe for progress: to achieve the best performance for a given compute budget, you should prioritize increasing model size far more aggressively than dataset size. This led to models like GPT-3, with 175 billion parameters trained on a "mere" 300 billion tokens—a ratio of less than two tokens per parameter. From your DevOps perspective, this is a clear resource allocation strategy: invest your FLOPs in a bigger architecture.
But what if that strategy was suboptimal? Science advances by questioning and refining previous findings. Two years after Kaplan's paper, researchers at DeepMind published "Training Compute-Optimal Large Language Models," a paper that re-evaluated this fundamental trade-off and arrived at a dramatically different conclusion.
This lesson focuses on these Chinchilla scaling laws. We will dissect how they revised the formula for compute-optimal training, explore the rigorous methodology DeepMind used to arrive at their new conclusions, and understand why their findings differed from Kaplan's. This investigation will reveal that many of the largest models of the era were, in fact, significantly undertrained.
A New Rule for Scaling: Balance is Key
The central finding of the Chinchilla paper is a direct rebuttal to the "model size first" approach. The DeepMind team found that for optimal performance, model size and the number of training tokens should be scaled in equal proportion.
Recall Kaplan's allocation:
- Optimal Model Size:
- Optimal Dataset Size:
The Chinchilla paper proposed a revised set of exponents:
- Optimal Model Size:
- Optimal Dataset Size:
This seemingly small change in exponents has enormous practical consequences. It implies that if you have 100 times more compute, you shouldn't build a model that's ~50 times bigger trained on ~2 times more data (Kaplan's advice). Instead, you should build a model that's 10 times bigger and train it on 10 times more data.
This led to the famous "Chinchilla rule": for compute-optimal training, a model should be trained on approximately 20 tokens for every parameter it has.

To begin, let's go directly to the source. The abstract and introduction of the paper provide a concise summary of this core argument.
Training Compute-Optimal Large Language Models
This is the original paper by Jordan Hoffmann et al. (2022) from DeepMind. Reading the opening sections will give you a direct, high-level summary of their core argument and how it contrasts with previous work.
Read the Abstract and the Introduction. Pay close attention to how they frame their research question and the immediate comparison they make with the findings of Kaplan et al. (2020).
Why the Discrepancy? Revisiting the Methodology
How could two different research groups, both conducting extensive experiments, arrive at such different conclusions? The answer lies in subtle but critical differences in experimental methodology. A key issue identified by the DeepMind team was the handling of the learning rate schedule.
As we discussed in the pre-training module, a common strategy is to use a learning rate that warms up and then decays over the course of training (e.g., a cosine schedule). The Kaplan et al. experiments used a fixed schedule length for all models. This meant that models trained on more data (i.e., for more steps) would have their learning rate decay to its minimum value relatively early, and then continue training with a tiny, ineffective learning rate for the remainder of the run. This systematically underestimated the benefit of training for longer on more data.
Professor Mohit Iyyer from UMass provides a succinct explanation of this issue.
UMass CS685 S23 (Advanced NLP) #18: Scaling laws of large language models
Professor Iyyer's lecture clearly summarizes the Kaplan et al. paper and its critical flaw, setting the stage for why the Chinchilla paper was necessary.
Watch the segment from this section on the issues in the Kaplan et al. experiments. The key point here is about the fixed learning rate schedule and how it disadvantaged longer training runs, leading to skewed conclusions.
The authors of the Chinchilla paper explicitly addressed this limitation. By carefully tailoring the learning rate schedule to match the number of training tokens for each run, they were able to get a much more accurate signal about the true value of additional data.
Training Compute-Optimal Large Language Models
The authors of the Chinchilla paper directly address why their findings differ from Kaplan et al. in their "Related Work" section.
Read the paragraph starting here. This text explicitly calls out the fixed learning rate schedule as a key reason for the different conclusions. This is a great example of the scientific process in action, where one research group identifies and corrects for limitations in a previous group's methodology.
Three Paths to the Same Conclusion
The strength of the Chinchilla paper lies in its rigorous methodology. Instead of relying on a single method, the researchers used three distinct approaches to estimate the optimal scaling law. The fact that all three converged on a similar result provides strong evidence for their conclusion.
Here's a brief overview of the three approaches:
-
Approach 1: Fixed Model Sizes. The team trained models of several fixed sizes (e.g., 70M, 1B, 10B parameters) and varied the number of training tokens for each. By plotting the loss curves, they could find the "lower envelope"—the optimal performance achievable for any given FLOPs budget—and deduce the model size and token count that achieved it.
-
Approach 2: IsoFLOP Curves. The team fixed several total compute budgets (e.g., FLOPs, FLOPs). For each budget, they trained various models, trading off parameters for tokens (e.g., a big model on few tokens vs. a small model on many tokens). Plotting loss against model size for a fixed budget results in a U-shaped "iso-FLOP" curve. The minimum of this curve reveals the optimal model size for that specific budget.
-
Approach 3: Parametric Loss Fitting. This approach models the final loss as a parametric function of model size () and dataset size (). The function they proposed is:
Here, represents the irreducible loss (the entropy of language), the term represents the error from finite model size, and the term represents the error from a finite number of training tokens. By training over 400 models with different and and fitting this function, they could solve for the optimal allocation mathematically.
The following segment from the Stanford lecture on scaling laws provides an excellent, detailed walkthrough of these three methods.
Stanford CS336 Language Modeling from Scratch | Spring 2025 | Lecture 9: Scaling laws 1
The Stanford lecture provides a clear and comprehensive walkthrough of the three distinct methodologies used in the Chinchilla paper to arrive at the compute-optimal scaling law.
Please watch the segment from this section covering the three methods. For each method, focus on understanding the experimental setup and how the optimal allocation is derived from the resulting plots.
As the lecturer notes, there was a fascinating follow-up story where other researchers discovered a minor curve-fitting error in Approach 3. When corrected, the result from Approach 3 aligned even more perfectly with the other two, strengthening the paper's overall conclusion.
The Proof: Chinchilla vs. Gopher
Armed with their new scaling laws, the DeepMind team put their hypothesis to the test. At the time, DeepMind's flagship model was Gopher, a 280B parameter model trained on 300B tokens, following the Kaplan-style philosophy.
The new scaling law predicted that for the same compute budget used to train Gopher, a much smaller model trained on far more data would be optimal. They designed Chinchilla: a 70B parameter model (4x smaller than Gopher) trained on 1.4 trillion tokens (~4.5x more data).
The result was a resounding success. Despite being significantly smaller, Chinchilla outperformed Gopher, GPT-3 (175B), and other larger models on a wide range of downstream tasks. This was concrete proof that the compute-optimal strategy had shifted.
The following article provides a clear, practical breakdown of the final equations and includes a worked example that makes the abstract formulas concrete—something that should resonate with your technical background.
Chinchilla Scaling Laws: Compute-Optimal LLM Training
This article breaks down the final scaling equations and provides a step-by-step example of how to use them to allocate a compute budget.
First, read the section on the equations to see the final power laws and the parametric loss function exponents. Then, carefully study the worked example. This will solidify your understanding of how a fixed compute budget translates into a specific model size and dataset size using the Chinchilla laws.
The Impact on the Field
The Chinchilla paper had an immediate and lasting impact. It became clear that many of the largest models were sitting in the "undertrained" region—they were too large for the amount of data they had seen. Subsequent major models, like Meta's Llama series, adopted the Chinchilla philosophy, opting for smaller parameter counts (e.g., 7B to 70B) but training them on trillions of tokens.
This heatmap vividly illustrates the shift. Models in the red zone are undertrained (too few tokens per parameter), while models in the green zone are closer to the compute-optimal Chinchilla ratio.

Conclusion
In this lesson, we've traced the evolution of scaling laws from the initial findings of Kaplan et al. to the crucial revisions introduced by the Chinchilla paper. This journey highlights the self-correcting nature of the scientific process and provides a deeper, more nuanced understanding of the resources required to build powerful language models.
Here are the key takeaways:
- Revised Allocation: The Chinchilla scaling laws revised the compute-optimal strategy, showing that model size and dataset size should be scaled equally ().
- The 20:1 Rule: This leads to a practical rule of thumb: for compute-optimal training, a model should see approximately 20 tokens per parameter.
- Methodological Rigor: The conclusion was supported by three independent experimental methods and confirmed by training Chinchilla (70B), which outperformed the much larger Gopher (280B) model using the same compute budget.
- Paradigm Shift: The findings revealed that previous large models like GPT-3 were significantly undertrained. This shifted the industry's focus from a pure race for parameter count to a more balanced approach that heavily emphasizes the quantity and quality of training data.
We have now established a robust quantitative framework for thinking about scale. But what happens at that scale? It turns out that simply making models bigger doesn't just lead to better performance on existing tasks; it can lead to entirely new, unpredicted behaviors. In our next lesson, we will explore these fascinating emergent capabilities, such as in-context learning, and discuss the idea that for LLMs, "more is different."