6.1.2 · D1Scaling & Efficient Architectures

Foundations — Compute-data-parameter tradeoffs

1,915 words9 min readBack to topic

This is the ground-floor page for Compute-data-parameter tradeoffs. The parent note throws around , , , FLOPs, loss , exponents , and the "6" in as if you already know them. Here we build every one from nothing, in an order where each rests on the previous. A smart 12-year-old should finish this page ready to read the parent.


0. The absolute starting point: what a model is

Figure — Compute-data-parameter tradeoffs

Look at the figure: the box has three dials on it. Real models have billions of dials, but the idea is identical. Training = automatically turning the dials until the guesses get good. That's the entire game. Every symbol below is about either the dials, the practice questions, or the effort of turning them.


1. — the number of parameters

The picture: is the size of the box in the figure above — a bigger box holds more dials. Why does the topic need ? Because more knobs means more capacity (see §5), but every knob also costs effort to train (see §3). is one of the two things we are trading off.


2. — the number of tokens

Figure — Compute-data-parameter tradeoffs

The picture: is the length of the tape of practice questions feeding into the box. Why does the topic need ? Because a model learns by being quizzed on data. More tokens ( larger) = more practice = better learning — up to a point. is the other thing we trade off against .


3. FLOP — one unit of computer effort

Why this unit and not "seconds"? Seconds depend on how fast your GPU is; FLOPs measure the work itself, independent of hardware. A faster chip does the same FLOPs in less time. So FLOPs let us compare training runs fairly. We need this before we can define the budget .


4. — the compute budget, and why

Now the key link. Each token, as it passes through the model, touches every knob a fixed number of times:

Figure — Compute-data-parameter tradeoffs

Look at the figure: effort is the area of a rectangle whose sides are and . This is the single most important picture in the whole topic — because if the area (budget) is fixed, then making one side longer forces the other side shorter. That's the trade-off, drawn as a rectangle. Every time the parent says "at fixed compute", picture holding this area constant while sliding the sides.

Related deep dives: FLOP accounting in Transformers pins down where the "6" is approximate; Inference cost vs training cost adds a second budget for serving the model.


5. — the loss, and capacity

Why the topic needs : it's the thing we are trying to make small. and are the dials we control; is the scoreboard. The parent's whole optimisation is "make as small as possible for a fixed ." See Overfitting and capacity for the -vs- balance, and Neural Scaling Laws for how falls as you scale.


6. Exponents and — reading power-law shorthand

Figure — Compute-data-parameter tradeoffs

Look at the figure: three curves, (straight line), (bends down), . Why does the topic need fractional exponents? Because when you double compute, the model should not double in size — it grows only by . The fraction is the answer to "how much bigger?" and it's always less than the full compute factor because you split growth between and .


The prerequisite map

model = box of knobs

N = number of knobs

D = tokens of practice data

FLOP = one arithmetic step

C = total FLOPs budget

C approx 6ND rectangle

capacity and overfitting

L = loss scoreboard

trade-off at fixed budget

exponents and proportional

N and D scale as powers of C

Compute-data-parameter tradeoffs

Each box on the left is defined on this page; they all flow into the parent topic at the bottom.


Equipment checklist

Test yourself — you should be able to answer each before opening the parent note.

What does count, and what picture is it?
The number of parameters (adjustable knobs); the size of the box of dials.
What is a token, and what does measure?
A token is a sub-word chunk of text; is the total number of tokens trained on — the length of the practice tape.
What is one FLOP?
One floating-point operation — a single multiply or a single add; the unit of computer effort.
How many FLOPs is one FMA?
Two — a fused multiply-add does a multiply and an add together.
What is and why is it fixed?
Total training compute in FLOPs (GPU-hours × FLOP/s); it's your budget, decided in advance.
Where does the "6" in come from?
2 FLOPs/param for the forward pass + 4 FLOPs/param for the backward pass = 6 FLOPs per parameter per token.
Why does fixing create a trade-off between and ?
is a rectangle of fixed area; making one side bigger forces the other smaller.
What is loss ?
A single number scoring how wrong the model's guesses are; training minimises it.
What is capacity, and what causes overfitting?
Capacity is how much a model can learn, set by ; overfitting is memorising data when is large relative to .
What does mean in plain words?
When compute rises, model size rises like — slower than compute itself, because growth is shared with data.
What are , , in the loss law?
Irreducible loss floor, penalty for too few parameters, penalty for too little data.