Equation 8 · The Deployment Envelope: Small Models Where the Power Is Not
What does this equation mean?
Read the formula alongside the article passage below. Each part has a deeper page with its role in the equation, the supporting passage and nearby citations.
This equation states a bound: one expression must stay on the indicated side of the other under the article’s assumptions. Read the equation part by part below; each part has a contextual explanation and a link to its mathematical background.
Read it piece by piece
Symbol T_tok
ok is a part of this expression. Its role is fixed by the surrounding article and by the operations shown in the formula.
Symbol B
the achievable memory bandwidth and I the operational intensity of the kernel.
subscript
The lower label selects a particular version, component, or indexed member of the quantity. For example, x₀ and xₜ can be values at different positions.
How to interpret it
With a fixed numerator, increasing a nonzero denominator reduces the fraction.
What the article says around this equation
Autoregressive decoding sits at the far left of that graph. Generating one token requires reading essentially every weight and the accumulated key-value cache once, and performing roughly two arithmetic operations per parameter. At one byte per weight the intensity is about two operations per byte; at four bits per weight, about four. Pope and colleagues formalised this partitioning problem for large transformers and showed how latency, throughput and cost trade off under different sharding strategies, with generation and prefill behaving as different regimes [ 3 ] . The bound that matters on a device follows immediately: if W bytes of weights and cache must cross the memory bus for each…
Read the full surrounding passage
Autoregressive decoding sits at the far left of that graph. Generating one token requires reading essentially every weight and the accumulated key-value cache once, and performing roughly two arithmetic operations per parameter. At one byte per weight the intensity is about two operations per byte; at four bits per weight, about four. Pope and colleagues formalised this partitioning problem for large transformers and showed how latency, throughput and cost trade off under different sharding strategies, with generation and prefill behaving as different regimes [ 3 ] . The bound that matters on a device follows immediately: if W bytes of weights and cache must cross the memory bus for each token and the sustained bandwidth is B , then the time per token cannot be less than . no matter how fast the arithmetic units are. As an arithmetic illustration with assumed values rather than a measurement of any product: a four-billion-parameter model at four bits per weight is roughly two gigabytes of weights, so a device sustaining fifty gigabytes per second cannot exceed about twenty-five tokens per second, and a device sustaining twenty-five gigabytes per second cannot exceed about twelve. Nothing in the model, the framework or the prompt changes that ceiling. Only fewer bytes or more bandwidth does.
Sources cited in the surrounding passage
These citations give research context. Read each source to check which claims it supports.
Return to The Deployment Envelope: Small Models Where the Power Is Not