Capability per Joule

Every model inherits two numbers from its stack: how much capability it gets per FLOP, and how many FLOPs it gets per joule. Pretraining sets most of the first. Infrastructure and the chip set the second. I think energy and efficiency are first principles of intelligence, so I have moved my research focus from robot world models to these two numbers.

Multiplied, the two numbers give capability per joule:

\[ \frac{\text{capability}}{\text{joule}} = \frac{\text{capability}}{\text{FLOP}} \times \frac{\text{FLOP}}{\text{joule}} \]

The formula is bookkeeping. It is true for any model. The claim is about who can move each factor. Pretraining moves the first factor through architecture, data, optimizer and learning-rate schedule. Infrastructure moves the second through kernels, memory traffic and communication; the chip sets its ceiling. Capability needs a fixed proxy, such as loss on fixed data or a fixed evaluation score.

An LLM is a system, and infrastructure and pretraining are its core. Gains in this layer transfer across models. A new world-model architecture raises capability per FLOP for one class of tasks. A better optimizer, or a kernel that moves fewer bytes, can help many models that share the same operators and hardware. That transfer is why I call this layer more fundamental.

Algorithms fit the hardware

Aidan Smith, a co-founder of Flapping Airplanes, gives an example from the brain. He says that signals in the brain are slow next to a GPU, which works in microseconds. He adds that the brain spends about 20 times more energy on white-matter wiring to get even that speed. His conclusion: “everything fits to the hardware that it’s given” (05:52).

If algorithms fit the hardware, the cost of the hardware is part of what makes an algorithm good: joules, bytes moved, microseconds.

What small experiments can already do

Two recent measurements show that small experiments can study this layer. Neither is in joules yet.

One-row BF16 GEMMs in a decode step are bound by bytes read from memory. Triton’s do_bench clears the L2 cache by writing zeros. The zeros leave dirty lines that must go back to memory first, and this adds 12–20 µs to these GEMMs on one A100. For one layer shape, the flush changed the rank of 9 of 96 Triton INT8 kernel configurations against cuBLAS. In this layer, the measurement is part of the research.

In a GPT-2-small-sized model, a simple momentum model predicts that the equilibrium effective learning rate of Muon is 24% below that of AdamW. The one run pair that reached equilibrium gave 23%. One pair cannot isolate momentum, and a gap of similar size also appears away from equilibrium, for another reason.

Where the claim stops

The strongest objection is historical. The largest past gains in capability per FLOP came from architecture and data, such as the transformer. I accept it. I put architecture inside pretraining, and I do not claim that kernels matter more than architecture.

Data is a limit that the formula hides. When the number or quality of tokens binds, FLOP efficiency does not help. Even Aidan’s lab, which bets on data efficiency, works toward it through new GPU primitives.

So the claim needs three conditions: compute and energy limit capability, data does not, and the capability proxy is stable. Under them, gains in this layer reach many models that share the same operators and hardware.