REVIEW 5 cited by
Estimating the Energy Footprint of Software Systems: a Primer
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
Signed reviews
read the original abstract
In Green Software Development, quantifying the energy footprint of a software system is one of the most basic activities. This documents provides a high-level overview of how the energy footprint of a software system can be estimated to support Green Software Development. We introduce basic concepts in the area, highlight methodological issues that must be accounted for when conducting experiments, discuss trade-offs associated with different estimation approaches, and make some practical considerations. This document aims to be a starting point for researchers who want to begin conducting work in this area.
Forward citations
Cited by 5 Pith papers
-
An Empirical Study on the Performance and Energy Usage of Compiled Python Code
On seven single-threaded Computer Language Benchmarks Game programs with no third-party libraries, Codon, PyPy, and Numba cut average execution time and energy by roughly 86 to 95% compared with CPython, while Nuitka ...
-
Language Models in Software Development Tasks: An Experimental Analysis of Energy and Accuracy
Larger language models do not reliably deliver higher accuracy on software tasks, and quantized large models can outperform full-precision medium models on energy and accuracy together.
-
Generating Energy-Efficient Code via Large-Language Models -- Where are we now?
Across 363 solutions on three hardware platforms, no LLM consistently matched a green software expert's energy efficiency, though some LLM-prompt combinations beat ordinary human code.
-
Static Metrics Are Insufficient: Predicting Java Method Energy Usage with Execution Time
Static code metrics yield near-zero predictive power for Java method energy; adding execution time raises R² to 0.46, showing energy is dominated by runtime behavior.
-
Strategies to Measure Energy Consumption Using RAPL During Workflow Execution on Commodity Clusters
Four energy measurement methods were compared on Kubernetes with Nextflow; shell-script and plugin approaches are effective, but concurrent tasks require heuristics for per-task attribution.
Discussion (0). Continue with ORCID to comment.