LLMsLoading progress…

Scaling and budgets

Describe a pretraining loop and reason about data, batch size, precision and a simplified compute budget.

Budgets: parameters, tokens and compute

A rough estimate for the compute of training a dense transformer is C ≈ 6 · N · D floating-point operations, where N is the number of parameters and D the number of training tokens. The worked example: N = 10⁶ and D = 10⁸ give 6·10¹⁴ FLOPs. If a machine really sustains 10¹² FLOP/s on the job, that is 600 seconds.

For a fixed C the formula shows the trade-off: a model twice as big can see only half as many tokens. Published scaling-law studies fit how loss varies with N, D and C, and use such fits to decide the split.

log10 of compute budget (FLOPs)10^14.8 = 6.03e+14
parameters Ntokens D = C / 6Ntokens per parameterseconds at 10¹² FLOP/s
1e+51.00e+910042.66603
1e+61.00e+8100.427603
1e+71.00e+71.004603
1e+81.00e+60.01603

At a fixed budget, a bigger model means fewer tokens. Empirical "scaling laws" describe how loss tends to change with N, D and C under the conditions studied, and help to choose a split. They are fits to experiments, not guarantees for every setting.

Choose a budget. Each row is a different split of the same compute.

Predict first. Does more model size always beat more data under every fixed budget?

Chapter context

Pretraining optimizes next-token predictions over a dataset. Its costs depend on the architecture, sequence lengths, implementation and hardware. A useful budget model states which work it approximates and which work it ignores.

Chapter reference: math, worked example & code

This section belongs to the whole chapter, so it is the same on every lesson in it and may cover a different lesson's topic. The code for the experiment you just ran is inside the experiment itself.

Math and notation

A commonly used rough dense-transformer training estimate is

C≈6ND,C\approx6ND,

with N model parameters, D training tokens and C floating-point operations. It omits some architecture-dependent work and is not a hardware throughput guarantee. Effective token batch is approximately B×T×AB\times T\times A for microbatch B, length T and A accumulation steps.

Worked example

For N=1 million parameters and D=100 million training tokens, the rough compute estimate is 6×10^6×10^8=6×10^14 FLOPs. A microbatch of 4 sequences of length 8 accumulated twice contributes 64 token positions per optimizer update. Neither calculation includes padding exclusions or communication time.

Reference code

The following example uses the Python standard library and does not call a remote service.

N,D=1_000_000,100_000_000
assert 6*N*D == 600_000_000_000_000
batch,length,accumulation=4,8,2
assert batch*length*accumulation == 64

Python examples are provided for study and local execution; this page does not execute Python.

Common mistakes

Compute-optimal ratios are model- and study-dependent. Train/test leakage can arise from shared documents and overlap. Tokens per update and optimizer steps are different units.