Intuition What this page is
The parent note gave you the formulas.
Here we drill every kind of problem the topic can throw at you: normal budgets, tiny
starved budgets, huge budgets, the degenerate case where one term dominates, limiting
behaviour as compute → ∞ , a real-world word problem, and an exam-twist. Each example
tells you which cell of the matrix it lives in.
One promise: no symbol appears before we say what it means. We reuse only these, all from
the parent — let us restate them in plain words so line one is readable by someone who has
never seen them.
Definition The five symbols, in plain words
N = number of parameters (the "size of the brain" — how many adjustable numbers the model has).
D = number of training tokens (how much text it reads — its "experience").
C = compute , measured in FLOPs (floating-point operations = raw arithmetic work). It obeys C ≈ 6 N D .
L = test loss , a single number saying how wrong the model is on unseen data. Lower is better.
E , A , B , α , β = fixed constants fitted from experiments. α ≈ 0.34 , β ≈ 0.28 .
The master law (parent) is
L ( N , D ) = E + N α A + D β B .
Read it as: floor you can never beat + penalty for too small a brain + penalty for too little reading .
Every problem in this topic is one of these cells. The examples below are labelled by cell.
#
Cell (scenario class)
What makes it distinct
Example
C1
Balanced optimum
N , D chosen at the compute-optimal split
Ex. 1
C2
Data-starved (D / N ≪ 20 )
Too big a model, too little data — B / D β dominates
Ex. 2
C3
Data-glutted (D / N ≫ 20 )
Too small a model, too much data — A / N α dominates
Ex. 3
C4
Scale-up map
Given k × compute, how to re-split N , D
Ex. 4
C5
Forecast a loss drop
Predict new L before/after scaling
Ex. 5
C6
Limiting / degenerate
D → ∞ or N → ∞ : what does L approach?
Ex. 6
C7
Diminishing-returns arithmetic
"How much compute to halve the reducible loss?"
Ex. 7
C8
Real-world word problem
Dollars, GPU-hours, a deadline
Ex. 8
C9
Exam twist
Sum-of-exponents trap / the "forget the 6" trap
Ex. 9
Prerequisite links if a cell feels shaky: Compute budgets & FLOPs , Overfitting vs underfitting , Kaplan scaling laws .
The figure above is our map: the black curves are lines of equal compute (each point on one
curve has the same C = 6 N D ). The red curve is the compute-optimal ridge — the best ( N , D ) for
each budget. Cells C2 and C3 are the two ways to fall off that red ridge.
Worked example Ex. 1 — Balanced optimum (cell C1)
You have C = 6 × 1 0 23 FLOPs. Using the heuristic D ≈ 20 N , find N and D .
Forecast: guess — will N be closer to 10 B or 100 B? (Feel it before computing.)
Write both constraints. C = 6 N D and D = 20 N .
Why this step? Two equations, two unknowns — a solvable system. The second is the Chinchilla rule of thumb.
Substitute D = 20 N into C = 6 N D . C = 6 N ( 20 N ) = 120 N 2 .
Why? Eliminate D so we have one unknown N .
Solve for N . N = C /120 = 6 × 1 0 23 /120 = 5 × 1 0 21 ≈ 7.07 × 1 0 10 .
Why? Just algebra on step 2. So N ≈ 71 B params.
Back out D . D = 20 N ≈ 1.41 × 1 0 12 = 1.4 T tokens.
Why? Plug N into D = 20 N .
Verify: 6 N D = 6 ( 7.07 × 1 0 10 ) ( 1.41 × 1 0 12 ) ≈ 6.0 × 1 0 23 ✓ matches the budget.
Notice this reproduces the real Chinchilla model (≈ 70 B, 1.4 T). The tokens-per-param
ratio is D / N = 20 by construction — dead centre of the red ridge.
Worked example Ex. 2 — Data-starved (cell C2)
Gopher-style: N = 280 B, D = 300 B tokens. Is it under- or over-sized? By how much is data short?
Forecast: is D / N above or below 20 ?
Compute the ratio. D / N = 300 B /280 B ≈ 1.07 tokens/param.
Why? The ratio vs the target 20 instantly tells you which term dominates.
Compare to the ideal. 1.07 ≪ 20 → severely data-starved ; the B / D β penalty is large.
Why? Small D ⇒ big B / D β . This is the over-model-under-data corner (Overfitting vs underfitting intuition: it's not classic overfit but wasted capacity).
What is its compute? C = 6 N D = 6 ( 2.8 × 1 0 11 ) ( 3 × 1 0 11 ) = 5.04 × 1 0 23 FLOPs.
Why? We need C to find the balanced alternative.
Rebalance at the same C using Ex. 1's method: N ⋆ = C /120 = 5.04 × 1 0 23 /120 ≈ 6.48 × 1 0 10 ≈ 65 B, and D ⋆ = 20 N ⋆ ≈ 1.30 × 1 0 12 .
Why? Shows the fix: shrink N by ~4×, grow D by ~4×, at nearly the same cost.
Verify: 6 N ⋆ D ⋆ = 6 ( 6.48 × 1 0 10 ) ( 1.30 × 1 0 12 ) ≈ 5.05 × 1 0 23 ✓ same budget. A 4× smaller, better-fed model — exactly the Chinchilla story.
Worked example Ex. 3 — Data-glutted (cell C3)
A tiny model N = 1 B trained on D = 500 B tokens. Which term dominates the loss? Is this efficient?
Forecast: D / N = ? — will it be far above or below 20 ?
Ratio. D / N = 500 B /1 B = 500 tokens/param.
Why? Compare to 20 : this is 25 × too data-heavy.
Which penalty dominates? 500 ≫ 20 ⇒ the model is too small ⇒ A / N α dominates; extra data barely helps.
Why? Big data drives B / D β tiny, but the brain can't represent more — capacity bottleneck.
Compute wasted? C = 6 ( 1 0 9 ) ( 5 × 1 0 11 ) = 3 × 1 0 21 FLOPs. Optimal N for this C : 3 × 1 0 21 /120 ≈ 5.0 × 1 0 9 = 5 B, i.e. you should have used a 5× bigger model.
Why? Confirms inefficiency: same compute, better split available.
Verify: balanced D ⋆ = 20 × 5 × 1 0 9 = 1 0 11 = 100 B, and 6 ( 5 × 1 0 9 ) ( 1 0 11 ) = 3 × 1 0 21 ✓ same budget. Lesson: both starvation (C2) and glut (C3) are off the red ridge.
Worked example Ex. 4 — Scale-up map (cell C4)
You have a compute-optimal model. Budget is multiplied by k = 8 . New N and D as multiples?
Forecast: guess the two multipliers — do they multiply to 8 ?
Recall the optimal exponents. N ∝ C 0.45 , D ∝ C 0.55 (parent, from β / ( α + β ) and α / ( α + β ) ).
Why? These say how each grows with compute.
Apply the factor k = 8 . N -multiplier = 8 0.45 , D -multiplier = 8 0.55 .
Why? If C → k C then N → k 0.45 N , D → k 0.55 D .
Numbers. 8 0.45 ≈ 2.55 , 8 0.55 ≈ 3.14 .
Why? Plug in. Data grows a touch faster, as expected.
Verify: the two multipliers must multiply to k because C = 6 N D forces the exponents to sum to 1 : 8 0.45 × 8 0.55 = 8 1.0 = 8 ✓. And 2.55 × 3.14 ≈ 8.0 ✓.
Worked example Ex. 5 — Forecast a loss drop (cell C5)
Ignore E . Currently A / N α = 0.10 and B / D β = 0.10 (a balanced model). You double both N and D . New reducible loss?
Forecast: more or less than a 10% drop?
New param term. Doubling N : A / ( 2 N ) α = 0.10 ⋅ 2 − α = 0.10 ⋅ 2 − 0.34 .
Why? ( 2 N ) − α = 2 − α N − α — the constant 2 − α factors out.
Evaluate. 2 − 0.34 ≈ 0.790 , so param term ≈ 0.0790 .
Why? Numeric.
New data term. B / ( 2 D ) β = 0.10 ⋅ 2 − 0.28 ; 2 − 0.28 ≈ 0.824 , so ≈ 0.0824 .
Why? Same trick with β .
Sum. New reducible loss ≈ 0.0790 + 0.0824 = 0.1614 vs old 0.20 .
Why? Loss terms add.
Verify: drop fraction = ( 0.20 − 0.1614 ) /0.20 ≈ 0.193 ≈ 19% ✓ (matches parent's "~20%"). Cost: 2 × 2 = 4 × compute. Balanced scaling means no single bottleneck is left — both terms fall together.
Worked example Ex. 6 — Limiting / degenerate (cell C6)
Fix N finite. Let D → ∞ (infinite data). What does L approach? Then let N → ∞ too.
Forecast: does L → 0 ? (Careful — trap.)
Data term as D → ∞ . B / D β → 0 because β > 0 and D β → ∞ .
Why? A positive power of infinity is infinity; its reciprocal is 0 .
So L → E + A / N α . The data penalty vanishes but the param penalty stays and the floor E stays .
Why? Only the B / D β term depended on D .
Now also N → ∞ . A / N α → 0 , leaving L → E .
Why? Same reciprocal-of-infinity logic.
Verify: at E = 0.15 , A / N α = 0.05 : with infinite data L → 0.15 + 0.05 = 0.20 ; with both infinite L → 0.15 . Key insight: you can never beat E — it is the irreducible Bayes floor. Infinite data alone is not enough; a finite brain still leaves A / N α .
Worked example Ex. 7 — Diminishing-returns arithmetic (cell C7)
The param penalty is A / N α with α = 0.34 . How much must you multiply N to halve this penalty?
Forecast: 2 × ? 4 × ? More?
Set up the ratio. We want A / ( m N ) α = 2 1 ⋅ A / N α , where m is the unknown multiplier.
Why? "Halve" means new penalty = old /2 .
Cancel A / N α . m − α = 2 1 , i.e. m − 0.34 = 0.5 .
Why? The constants divide out; only the multiplier's power survives.
Solve for m . Raise both sides to − 1/ α : m = 0. 5 − 1/0.34 = 2 1/0.34 .
Why? Undo the exponent by its reciprocal.
Evaluate. 1/0.34 ≈ 2.94 , so m ≈ 2 2.94 ≈ 7.66 .
Why? Numeric.
Verify: 7.6 6 − 0.34 ≈ 0.500 ✓. To halve just the param part of the loss you need almost 8× the parameters — that is what "slow, diminishing power-law returns" means concretely.
Worked example Ex. 8 — Real-world word problem (cell C8)
Your cluster does 2 × 1 0 18 FLOPs/second. You may run for 10 days . Assuming full utilisation, what is the compute-optimal ( N , D ) , and how many tokens per parameter?
Forecast: roughly what size model — millions, billions, or trillions of params?
Total compute. Seconds in 10 days = 10 × 86400 = 8.64 × 1 0 5 s. C = 2 × 1 0 18 × 8.64 × 1 0 5 = 1.728 × 1 0 24 FLOPs.
Why? Compute = rate × time; converts a deadline into a budget.
Optimal N (Ex. 1 method): N = C /120 = 1.728 × 1 0 24 /120 = 1.44 × 1 0 22 = 1.2 × 1 0 11 = 120 B.
Why? Same balanced-split algebra with D = 20 N .
Optimal D . D = 20 N = 2.4 × 1 0 12 = 2.4 T tokens.
Why? Chinchilla rule.
Tokens/param. D / N = 20 by construction.
Why? Sanity: we built it on the ridge.
Verify: 6 N D = 6 ( 1.2 × 1 0 11 ) ( 2.4 × 1 0 12 ) = 1.728 × 1 0 24 ✓ exactly the budget. Units check: [ FLOPs/s ] × [ s ] = [ FLOPs ] ✓.
Worked example Ex. 9 — Exam twist: the two classic traps (cell C9)
(a) A student writes N ∝ C 0.45 and D ∝ C 0.60 . Spot the error.
(b) Another writes C = N D and gets compute 8 × too small. Why?
Forecast: which single check kills (a) instantly?
(a) Sum test. Exponents must satisfy 0.45 + (D-exp) = 1 because C = 6 N D forces N ∝ C a , D ∝ C b with a + b = 1 .
Why? Product N D ∝ C a + b must be ∝ C 1 .
Apply. 0.45 + 0.60 = 1.05 = 1 → impossible . Correct value is 0.55 .
Why? Fails the sum test; the D-exponent was mis-stated.
(b) The missing 6. C = 6 N D , not N D . Dropping the 6 undercounts by exactly the factor 6 (2 for multiply-add, ×3 for forward+backward).
Why? The 6 encodes the arithmetic per token per parameter (Compute budgets & FLOPs ).
Correct the claim. "8× too small" is loose — the true factor is 6 , so the student's error is a 6 × undercount.
Why? Restore the constant.
Verify: (a) 0.45 + 0.55 = 1.00 ✓ (the fixed pair sums to 1; the student's 1.05 did not). (b) ratio 6 N D / ( N D ) = 6 ✓.
Mnemonic The three quick tests you now own
Ratio test: compute D / N . Below 20 → starved (C2). Above 20 → glutted (C3). At 20 → balanced (C1).
Sum test: the C -exponents of N and D always sum to 1 .
Six test: any FLOP count without a 6 (dense transformer) is wrong by a factor of 6.
Recall Self-quiz (reveal after answering)
Compute-optimal N , D for C = 6 × 1 0 23 ? ::: N ≈ 71 B, D ≈ 1.4 T (Ex. 1).
Multiplier on N and D when compute × 8 ? ::: 8 0.45 ≈ 2.55 and 8 0.55 ≈ 3.14 (Ex. 4).
Doubling balanced N , D drops reducible loss by roughly? ::: ~19–20% (Ex. 5).
As D → ∞ with N finite, L → ? ::: E + A / N α — data penalty gone, floor and param penalty remain (Ex. 6).
Factor on N needed to halve the param penalty? ::: 2 1/0.34 ≈ 7.66 (Ex. 7).
Why can't N -exp and D -exp both be 0.6? ::: They must sum to 1 (Ex. 9a).
Related: Kaplan scaling laws (the earlier, over-param-tilted fit), Mixture-of-Experts (changes the effective N vs FLOPs relationship), Learning rate schedules (affects the fitted constants but not the exponent logic).