Skip to content
NewA calmer, faster ZeroHour

Token-Energy Law ties LLM decode joules to active bytes and time

Original title: The Token-Energy Law of LLM Decode: Active Bytes and Realized Time Account for Joules per Token

arXiv cs.AI / cs.LG / cs.CLby Chenxu Niu ()1 min read1 · 1 read
AI summary · x-ai/grok-4.7Summaries by Vani AI

Held-out energy estimates on Hopper and Blackwell stayed within 3.73% of measured means.

A paper presents the Token-Energy Law, an affine model of GPU-board energy per output token for dense, full-history decoding. It uses active bytes—shared dense weights versus private KV history—and realized decode time, with coefficients fit per model and hardware setup. Experiments cover three models in BF16 on NVIDIA Hopper and Blackwell, including two-GPU tensor parallelism on Hopper.

Key facts
  • Batching amortizes shared-weight work; longer histories raise private KV demand.
  • Tests include two-GPU tensor parallelism on Hopper.
  • Fixed coefficients plus observed decode time produced the held-out estimates.
  • The law targets dense full-history decoding, not other serving modes.
Explain this AI news with Vani AIWhat was announced, what is new and why it matters, in a new chat

From the original article

1 min read at arxiv.org

Energy-efficient deployment of large language models requires understanding how model architecture, hardware, and serving settings shape energy per generated token. We introduce the Token-Energy Law, a compact, interpretable model of GPU-board energy per output token for dense, full-history decoding. It relates token energy to two core dimensions: active bytes and realized decode time.

arXiv cs.AI / cs.LG / cs.CL

By Chenxu Niu · arxiv.org

Read the full article at arXiv cs.AI / cs.LG / cs.CL

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.