Certified into the record
The exact text we saved
This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.
TRUVACE RECORD VERSION record: TRV-2026-2619 version: 1 kind: certified reason: Certified into the record timestamp: 2026-11-12T08:04:42.094753Z status: published lens: p_space sector: climate headline: MLPerf Power: Addressing the Artificial Intelligence Power Wall dek: Power has become the defining constraint for modern machine learning, from milliwatt edge devices to multi-megawatt training clusters. Across this nine-order-of-magnitude span, the field has lacked a consistent way to measure and compare energy efficiency. We present MLPerf Power, a cross-scale energy benchmarking methodology that adapts instrumentation while preserving common measurement principles and reports shared metrics such as samples per joule and tokens per joule. The methodology has produced 1,841 repr… gain_title: (none) problem_title: A benchmark of 1,841 submissions from 60 systems found that easy AI energy-efficiency gains are plateauing and that energy use scales nonlinearly with accelerator count. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: A benchmark of 1,841 submissions from 60 systems found that easy AI energy-efficiency gains are plateauing and that energy use scales nonlinearly with accelerator count. problem_evidence: easy efficiency gains are plateauing | energy scales nonlinearly with accelerator count quick_read: The MLPerf Power methodology measures energy efficiency for machine learning systems ranging from milliwatt edge devices to multi-megawatt training clusters, a span of nine orders of magnitude. It reports shared metrics such as samples per joule and tokens per joule, and has produced 1,841 reproducible submissions from 60 systems. Analysis of that corpus shows that easy efficiency gains are plateauing and that energy scales nonlinearly with accelerator count. It also shows that low-precision innovation has substantially reduced the cost of high-accuracy inference. For large language model inference, the authors report that sparse mixture-of-experts models pay a memory-bandwidth penalty that contradicts training intuitions. They say the public corpus already informs industry roadmaps, infrastructure planning and verified carbon accounting. limitation: tag: Evidence-backed problem key_points: The methodology adapts instrumentation across scales while keeping common measurement principles. | It yielded 1,841 reproducible submissions from 60 systems. | Metrics include samples per joule and tokens per joule. | Energy scales nonlinearly with accelerator count. | Low-precision innovation has substantially reduced the cost of high-accuracy inference. | Sparse mixture-of-experts LLMs pay a memory-bandwidth penalty during inference that contradicts training intuitions. rundown: The paper describes MLPerf Power as a cross-scale energy benchmarking methodology. It covers systems from milliwatt edge devices to multi-megawatt training clusters, where the field previously lacked a consistent way to measure and compare energy efficiency. The submission corpus shows that easy efficiency gains are plateauing, and that adding accelerators increases energy use nonlinearly. Low-precision techniques have substantially lowered the cost of running high-accuracy inference. Extending the benchmark to LLM inference, the authors show that sparse mixture-of-experts models pay a memory-bandwidth penalty. The publicly accessible corpus is said to inform industry roadmaps, infrastructure planning, and energy-aware optimization and verified carbon accounting. sources: - peer_reviewed | IEEE Micro | https://doi.org/10.1109/mm.2026.3700126 | 2026-06-04 prev: 0000000000000000000000000000000000000000000000000000000000000000
- SHA-256 hash
- 21cc2def28d1981cada0e96e8c2f12a21fae7ba5981753c245da4d01b648d8d3
- Previous version’s hash
- 0000000000000000000000000000000000000000000000000000000000000000
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2619 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.
ace