6.1.1 · D3Scaling & Efficient Architectures

Worked examples — Neural scaling laws (Chinchilla, compute-optimal)

2,251 words10 min readBack to topic

The scenario matrix

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 chosen at the compute-optimal split Ex. 1
C2 Data-starved () Too big a model, too little data — dominates Ex. 2
C3 Data-glutted () Too small a model, too much data — dominates Ex. 3
C4 Scale-up map Given compute, how to re-split Ex. 4
C5 Forecast a loss drop Predict new before/after scaling Ex. 5
C6 Limiting / degenerate or : what does 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.


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

The figure above is our map: the black curves are lines of equal compute (each point on one curve has the same ). The red curve is the compute-optimal ridge — the best for each budget. Cells C2 and C3 are the two ways to fall off that red ridge.


Worked examples


Recall Self-quiz (reveal after answering)

Compute-optimal for ? ::: B, T (Ex. 1). Multiplier on and when compute ? ::: and (Ex. 4). Doubling balanced drops reducible loss by roughly? ::: ~19–20% (Ex. 5). As with finite, ? ::: — data penalty gone, floor and param penalty remain (Ex. 6). Factor on needed to halve the param penalty? ::: (Ex. 7). Why can't -exp and -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 vs FLOPs relationship), Learning rate schedules (affects the fitted constants but not the exponent logic).