mlcommons / mlcommons/inference

[Discussion] Adding energy consumption metrics to MLPerf Inference Benchmark

Open
#2,558 18 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.6k
Forks
650
Avg merge
1d 22h
Merged PRs (30d)
6

Description

Discussion: Energy Metrics for MLPerf Inference

Context

MLPerf Inference currently reports throughput and latency metrics. As AI sustainability becomes a key concern, standardized energy efficiency metrics would complement existing benchmarks.

Observation

Through systematic benchmarking of quantized LLM inference (NF4, INT8, FP16) across NVIDIA Ada Lovelace and Blackwell architectures, we found that:

  1. Quantization's energy impact is non-trivial and model-size dependent
  2. For models <3B parameters, NF4 quantization increases energy by 25-56%
  3. INT8 mixed-precision adds 17-33% energy overhead vs FP16
  4. These trade-offs are not captured by throughput/latency alone
Suggestion

Consider adding optional energy reporting to the MLPerf Inference benchmark:

  • Energy per query/token (J)
  • Average power draw (W)
  • Energy efficiency (tokens/J)

This would enable apples-to-apples energy comparison across hardware and quantization configurations.

Data
Related

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is identified. Start by reviewing the existing MLPerf Inference benchmark metric-reporting flow and the proposed energy measurements, then determine where an agreed measurement protocol would fit. Done requires a maintainer-approved scope and implementation plan for energy per query/token, average power, and energy efficiency.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.