6.1.1 · D1Scaling & Efficient Architectures

Foundations — Neural scaling laws (Chinchilla, compute-optimal)

2,516 words11 min readBack to topic

Before you can trust a single line of the parent note, you must own every letter it throws at you. Below, each symbol appears in the order it becomes needed — nothing uses anything above it that wasn't already defined.


1. What is a "model" and what is ?

Picture a mixing desk in a music studio: hundreds of knobs, each nudging the sound. A neural net is the same idea but with billions of knobs. counts them.

Look at Figure 1: each little circle is one knob, and the pink arrow reminds you that counting every knob on the board gives you .

Figure — Neural scaling laws (Chinchilla, compute-optimal)
  • small → few knobs → the machine is too simple to capture complicated patterns.
  • large → many knobs → it can represent complicated patterns (whether it learns to is a separate question — that's where data comes in).

Why the topic needs : "make the model bigger" literally means "increase ". You cannot talk about the size–vs–data trade-off without a number for size.

Related reading once you're comfortable: Transformer architecture (the specific machine whose knobs we're counting).


2. What is — how much experience?

Picture a stack of flashcards. Each card is one token the model sees. is the height of the stack.

  • small → little practice → even a big-brained model hasn't seen enough to learn.
  • large → lots of practice → the model can pin down what its many dials should be set to.

Why the topic needs : "feed it more data" means "increase ". Size () and experience () are the two things we trade off.


3. What is "loss" and the symbol ?

Think of as a golf score: lower is better, and zero (perfect) is basically impossible to reach.

Because depends on both how big the model is and how much it studied, we write it as a function of both: — read aloud as " of and ", meaning the loss you get for that particular choice of size and data.

Look at Figure 2: the blue curve is the loss dropping as you pour in more size and data. Notice it flattens toward a dashed pink line — a mistake-floor it can never cross. That floor is real and important, and we give it the symbol in Section 6 (for now just notice the curve stops falling).

Figure — Neural scaling laws (Chinchilla, compute-optimal)

Why can loss never reach zero? Because language itself is partly unpredictable — no one can guess the exact next word every time — so there is always some leftover, unavoidable mistake. Section 6 names it.


4. Functions and notation

Picture a vending machine: press a button (input), get a snack (output). later means "a machine that now only needs one input, ."

Why the topic needs this: the whole derivation is about finding which input to a function gives the smallest output. You must be at ease reading and before Step 2 of the parent.


5. Powers, and negative powers like

The little raised number (, or the Greek letter ) is called the exponent — it controls how fast the growing or shrinking happens.

Look at Figure 3: three curves of for different exponents. Every one sags toward zero as grows, and the bigger the exponent, the faster it sags — that's the whole meaning of "the size of controls the speed."

Figure — Neural scaling laws (Chinchilla, compute-optimal)
  • with : bigger model → smaller mistake-term.
  • The size of says how quickly that term shrinks. (Note: this shrinking only works because is positive — a negative would make the term grow, which is the wrong physics.)

Why the topic needs this: the loss formula is built entirely from terms like and . If you can't read a negative power, the central equation is gibberish.


6. The Greek letters: (exponents) and (constants)

Picture a race: and are where two runners start, and are their speeds, and is the finish line neither can cross.

These are not chosen by us — they are fitted (measured) by training many models and seeing what numbers make the formula match reality.

Putting sections 1–6 together, the parent's central equation now reads with zero mystery:

Recall Why can't loss reach zero?

Because : there is always some inherent randomness/ambiguity in the data (the finish line neither runner can cross). ::: The irreducible floor is a positive constant; the two power-law terms can shrink toward zero but remains.


7. "Power law" vs "exponential" — and diminishing returns

Why the topic needs this: the phrase "diminishing returns = power law" is the reason scaling curves are smooth and predictable — the foundation of the whole field.


8. The symbol ("proportional to")

Picture two gears meshed together: turn one, the other turns in fixed ratio. is that fixed-ratio link, with the ratio left unnamed.

Why the topic needs this: the headline results and are stated with because only the exponent (how growth scales) is the interesting part.


9. FLOPs, compute , and the number

Picture a factory: workstations, items on the belt; each item visits each station and each visit costs a fixed 6 units of work.

Why the topic needs this: is the budget constraint. It locks and together — spend more on one, you have less for the other. That single equation is what turns "scaling" into an optimization problem. See Compute budgets & FLOPs.


10. "Constraint" and "optimum" — the shape of the whole problem

Picture a fence enclosing a field (the constraint) and you rolling a ball to find the lowest dip inside the fence (the optimum).

Why the topic needs this: the entire "HOW to derive" section is just "roll the ball to the lowest allowed point." Recognising it as constrained optimization tells you why calculus (setting a slope to zero) shows up next.


11. Slope, derivative, and "set it to zero"

Look at Figure 4: the blue curve is a valley (U-shape). The pink arrows show why it's a valley — the left branch falls (too few dials) and the right branch rises (the fixed budget forces down). The yellow dot marks the flat bottom, where the tangent line is horizontal, i.e. slope — that is .

Figure — Neural scaling laws (Chinchilla, compute-optimal)

Here the loss-vs- curve is unimodal: one term () always falls as grows, the other ( after substituting the budget) always rises — their sum makes a single U-shaped dip with exactly one flat bottom. (This "one always down, one always up" picture only holds because both and .)

Why the topic needs this: Step 3 of the parent differentiates and sets to zero. Without knowing "slope at the bottom," that step looks like magic.


Prerequisite map

Parameters N = model size

Loss L of N and D

Tokens D = data amount

Powers and negative exponents

Loss formula E plus A over N to alpha plus B over D to beta

Constants A B E and exponents alpha beta

Power law and diminishing returns

Constrained optimization

FLOPs and C equals 6 N D

Proportional to symbol

N and D scale with C

Derivative slope equals zero at minimum

Chinchilla compute-optimal split


Equipment checklist

Test yourself — you're ready for the parent note only when each line's answer comes instantly.

What does count, in one phrase?
The number of parameters (adjustable dials) in the model.
What does count?
The number of training tokens (total practice material) the model reads.
Read aloud and say what it returns.
"Loss of and " — the average mistake for that model size and data amount; one number out.
Rewrite without a negative exponent.
— it shrinks toward zero as grows (because ).
Which symbols are exponents and which are constants in ?
are exponents (growth speed, both positive); are constants ( is the irreducible floor).
What is the difference between a power law and an exponential here?
Power law puts the variable in the base () — slow diminishing returns to a floor; exponential puts the variable in the exponent () — runaway growth. Loss follows a power law.
What does mean?
"Proportional to" — grows in fixed ratio, exact multiplier ignored.
State the compute formula and where the 6 comes from.
; (multiply-add) (forward + backward forward).
What kind of problem is "best split of compute"?
Constrained optimization — minimise subject to fixed.
Why do we set the derivative (slope) to zero?
The bottom of the valley is flat; slope locates that minimum, and the curve is unimodal (since ) so it's the true minimum.

Once every line above is second nature, jump back to the parent topic and the derivation will read like plain English. For neighbouring ideas you'll meet soon, see Kaplan scaling laws, Overfitting vs underfitting, Mixture-of-Experts, and Learning rate schedules.