RESILIENCE REFERS TO THE CAPACITY TO RECOVER FROM DIFFICULTIES, ADAPT TO CHANGE, AND KEEP MOVING FORWARD DESPITE CHALLENGES. RESILIENCE REFERS TO THE CAPACITY TO RECOVER FROM DIFFICULTIES, ADAPT TO CHANGE, AND KEEP MOVING FORWARD DESPITE CHALLENGES. RESILIENCE REFERS TO THE CAPACITY TO RECOVER FROM DIFFICULTIES, ADAPT TO CHANGE, AND KEEP MOVING FORWARD DESPITE CHALLENGES.
Back to Blog

Position · Scaling

The Data Wall

Transformer scaling was a bet on abundant data. That bet is being called.

Abstract

For five years the dominant strategy in machine learning has been to make transformers larger and feed them more text. The scaling laws that justified this are real, but they have a term most summaries omit: data. Compute-optimal training requires tokens to grow in step with parameters, and the stock of high-quality human text is finite. Recent estimates place its effective exhaustion within this decade. Repeating data, generating synthetic data, and scraping more aggressively each push the wall back by a few years at most, and some carry their own degradation. We argue the conclusion is not 'scaling is over' but rather 'scaling on a frozen, context-bounded architecture is over' — which reframes the data wall as a reason to change the architecture, not to abandon learning at scale.

In 2020 the recipe for a better language model became refreshingly simple: add parameters, add compute, add data, and loss falls along a smooth power law 1. That predictability is what unlocked the last half-decade of capital. You could write a check for a training run and forecast the result.

The recipe had three ingredients, and the public conversation collapsed them into one — compute. But the original scaling laws were explicit that data is a separate, co-equal term, and the field’s own course-correction made that impossible to ignore.

Chinchilla moved the bottleneck

DeepMind’s 2022 Compute-Optimal result — “Chinchilla” — showed that the large models of the day were badly undertrained 2. For a fixed compute budget, parameters and training tokens should scale in roughly equal proportion; the rule of thumb that emerged was on the order of twenty tokens per parameter. A 70B-parameter Chinchilla trained on 1.4 trillion tokens beat the 280B-parameter Gopher trained on far fewer.

The headline was “smaller models can be better.” The consequence, less discussed, was that every future unit of compute now comes with a data invoice. You cannot spend your way past the bottleneck with more GPUs alone; compute-optimal scaling requires the token count to rise with the parameter count. The question becomes unavoidable: how many high-quality tokens exist?

How much text is there, really?

The most careful public attempt to answer this comes from Epoch AI 3. Estimating the stock of human-generated public text and projecting training-set growth, they conclude that the usable stock will be effectively exhausted within this decade — with central estimates clustering around 2026–2032 depending on how aggressively data is reused. The frontier is not approaching the wall; it is already scraping along it.

demand > supply stock of human text training-set size time →
Schematic. The stock of high-quality human text grows roughly with population and digitization — slowly and saturating. Compute-optimal training-set size grows with the compute being deployed — far faster. The two were never going to stay compatible; the only question was the crossing date.

The escape hatches buy years, not decades

Three responses are usually offered. Each helps, none dissolves the constraint.

Repeat the data. Muennighoff et al. studied training in the data-constrained regime directly and found that repeating a corpus for up to roughly four epochs is nearly as good as fresh tokens 4. That is a genuine and useful result — but it is a constant-factor reprieve. Past a handful of epochs the marginal value of another pass decays toward zero. Four epochs is a one-time multiplier, not a new supply curve.

Generate synthetic data. Promising for narrow, verifiable domains (math, code) where a checker provides ground truth. But training a model on the unfiltered output of models degrades it: Shumailov et al. show that recursive training on generated data causes model collapse, with tails of the distribution disappearing first 5. Synthetic data can re-package what a model already knows; it cannot conjure new information about a world it has never observed.

Scrape harder. Multimodal corpora, transcribed video, and more languages extend the runway. But these are still the same kind of artifact — a static, human-produced record of the past, scraped once and frozen into weights.

The constraint is structural, not logistical

Here is the reframe. The shortage is not of information in the world — the world produces an unimaginable amount every second. The shortage is of information in the format this architecture can consume: pre-existing, human-authored, batch-collected text.

That last clause is the real constraint, and it is a property of the architecture, not of the planet. A transformer is trained once on a fixed corpus and then frozen at deployment. It cannot turn the experience it generates while running — the actions it takes, the corrections it receives, the outcomes it observes — back into learning. So the only data it can ever use is data that already existed before training began. The well is dry because we built a machine that can only drink from wells.

This is why we read the data wall not as an obituary for scale, but as a specification for what comes next. The lesson of the last decade — that general methods riding more computation win 6 — still holds. What has to change is the source of experience: from a finite archive of human text to the open-ended, continuously generated stream of an agent acting in the world 7. The systems already exist that produce that stream — every robot on a line, every agent doing a task 8. What is missing is an architecture that can learn from it as it arrives.

That architecture — bounded in state, continual in learning — is the subject of the companion post.


## References
  1. Kaplan, J., McCandlish, S., Henighan, T., et al. (2020). Scaling Laws for Neural Language Models. arXiv:2001.08361.
  2. Hoffmann, J., Borgeaud, S., Mensch, A., et al. (2022). Training Compute-Optimal Large Language Models (Chinchilla). arXiv:2203.15556.
  3. Villalobos, P., Ho, A., Sevilla, J., Besiroglu, T., Heim, L., & Hobbhahn, M. (2024). Will We Run Out of Data? Limits of LLM Scaling Based on Human-Generated Data. Epoch AI. arXiv:2211.04325.
  4. Muennighoff, N., Rush, A. M., Barak, B., et al. (2023). Scaling Data-Constrained Language Models. NeurIPS. arXiv:2305.16264.
  5. Shumailov, I., Shumaylov, Z., Zhao, Y., Gal, Y., Papernot, N., & Anderson, R. (2024). AI Models Collapse When Trained on Recursively Generated Data. Nature 631, 755–759.
  6. Sutton, R. (2019). The Bitter Lesson.
  7. Silver, D., & Sutton, R. (2025). Welcome to the Era of Experience.
  8. Open X-Embodiment Collaboration (2024). Open X-Embodiment: Robotic Learning Datasets and RT-X Models. ICRA. arXiv:2310.08864.