Skip to content

Commit 5c57fed

Browse files
committed
Fix ML.ENERGY Benchmark paper entry
1 parent 2683f20 commit 5c57fed

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

source/_data/SymbioticLab.bib

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2152,7 +2152,7 @@ @InProceedings{mlenergy-benchmark:neuripsdb25
21522152
publist_confkey = {NeurIPS'25 D&B},
21532153
publist_link = {paper || mlenergy-benchmark-neuripsdb25.pdf},
21542154
publist_link = {code || https://github.com/ml-energy/benchmark},
2155-
publist_badge = {Spotlight Paper (acceptance rate: 2.81%)},
2155+
publist_badge = {Spotlight},
21562156
publist_abstract = {
21572157
As the adoption of Generative AI in real-world services grow explosively, energy has emerged as a critical bottleneck resource. However, energy remains a metric that is often overlooked, under-explored, or poorly understood in the context of building ML systems. We present the ML.ENERGY Benchmark, a benchmark suite and tool for measuring inference energy consumption under realistic service environments, and the corresponding ML.ENERGY Leaderboard, which have served as a valuable resource for those hoping to understand and optimize the energy consumption of their generative AI services. In this paper, we explain four key design principles for benchmarking ML energy we have acquired over time, and then describe how they are implemented in the ML.ENERGY Benchmark. We then highlight results from the early 2025 iteration of the benchmark, including energy measurements of 40 widely used model architectures across 6 different tasks, case studies of how ML design choices impact energy consumption, and how automated optimization recommendations can lead to significant (sometimes more than 40\%) energy savings without changing what is being computed by the model. The ML.ENERGY Benchmark is open-source and can be easily extended to various customized models and application scenarios.
21582158
}

0 commit comments

Comments
 (0)