Where Does the Energy Go? Profiling LLM Agent Inference on Blackwell GPUs
Fields
papers/where-does-the-energy-go-blackwell-profilingNotes
THE DISTINCTIVE CONTRIBUTION IN THIS SLICE IS THE 41-45% GAP AND THE MEASUREMENT METHODOLOGY THAT PRODUCES IT. A single-platform measurement paper, so it should not be over-read, but the methodological claim is the transferable part: NVML alone is not a system energy measurement, and any cost-per-token model derived from GPU board power is understating by roughly half. The 400-600 W flat band plus the sharp 300 W cliff is the most immediately actionable free lunch in the whole power slice - a wide cap range that costs nothing in throughput for memory-bandwidth-bound decode. The 'less than 1% per-token difference between thinking-enabled and thinking-disabled' result is the useful corrective to intuition: extended thinking does not make each token more expensive, it just produces more of them. The 63x agentic figure is the under-batching trap that breaks naive cost-per-token arithmetic on agentic traffic. Distinctive angle: this is component-level and phase-level power MEASUREMENT on datacenter parts, which is the datacentre-systems measurement line, not the algorithmic-efficiency or carbon-accounting line. Measured on 2x RTX PRO 6000 Blackwell - workstation-class parts, not rack-scale - so percentages transfer more safely than absolute watts. Read alongside gotchas/short-benchmark-not-representative-of-sustained-serving and gotchas/idle-and-underbatched-fleet-can-cost-more-than-busy-fleet.
AFFILIATIONS BACKFILLED 2026-10-04 (paper-fields pass, agent w3p): OpenAlex institutions field (HKU). Filled from the API/PDF rather than from memory, because an affiliation is a fact about a specific paper's author block and inference from the author's employer history is how wrong affiliations get shipped.
VENUE_TRACK BACKFILL 2026-10-04 (paper-fields pass, agent w3p): venue_track 'unknown'. `venue` is 'arxiv-preprint', which means no peer-reviewed venue has been established for this work as of the verification date, so the track genuinely is not known. 'unknown' is used here rather than leaving the field null or guessing 'main': the schema separates 'unknown' from 'main' precisely so that an unprereviewed preprint is not silently counted as main-track work. This annotation is what lets a downstream filter distinguish 'peer reviewed, main track' from 'not peer reviewed' without inferring it from the venue string.