Metraipolis › archive › dc_fe73ec661d76
Garbage Collection and Energy Consumption in Java: A Controlled Study Across Workloads and JDKs — arXiv:2608.19520
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2608.19520
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-18T11:44:45.138Z
- SHA-256 of the archived text
77b82fed2759a22a769c9874887493f5c65966389b1177a88aa0d0f3031d1384- Stable URL of this page
https://metraipolis.com/documento/dc_fe73ec661d76
How to cite
Garbage Collection and Energy Consumption in Java: A Controlled Study Across Workloads and JDKs — arXiv:2608.19520 — arXiv (en), https://arxiv.org/abs/2608.19520 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_fe73ec661d76 (Metraipolis archive dc_fe73ec661d76, sha256 77b82fed2759a22a769c9874887493f5c65966389b1177a88aa0d0f3031d1384)
BibTeX
@misc{dcfe73ec661d76,
title = {Garbage Collection and Energy Consumption in Java: A Controlled Study Across Workloads and JDKs — arXiv:2608.19520},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2608.19520},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_fe73ec661d76; sha256 77b82fed2759a22a769c9874887493f5c65966389b1177a88aa0d0f3031d1384},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2608.19520. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
Garbage-collector selection is a low-effort configuration decision that can influence both the performance and energy consumption of Java applications. However, it remains unclear whether aggregate energy rankings among collectors generalise across heterogeneous applications, workload intensities, and JDK distributions. This study presents a controlled empirical evaluation of Serial, Parallel, and G1 garbage collection across three Java applications, three workload intensities, and two JDK distributions: OpenJDK and Oracle JDK. Using EnergiBridge, processor-package energy consumption and execution time were measured and complementary energy-performance metrics derived. Across all evaluated configurations, Parallel recorded the lowest mean energy consumption (839.8 J), followed closely by Serial (857.6 J) and G1 (969.0 J), but an RCBD ANOVA did not establish a statistically reliable collector effect. Workload intensity, by contrast, was a significant driver of energy consumption, with heavy workloads consuming substantially more energy than light or medium workloads regardless of collector. Energy consumption showed a moderate positive association with execution time (r = 0.33), indicating that longer-running configurations tended toward higher energy use, though the relationship was far from proportional. No statistically significant energy difference was found between OpenJDK and Oracle JDK. Overall, the results do not support a universally energy-optimal garbage collector; instead, workload intensity emerges as the more reliable lever for managing Java energy consumption, and collector selection should be treated as an application-specific tuning decision supported by measurement on the target system rather than aggregate rankings alone. Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-08-21 in cs.PF). Categorie arXiv: Software Engineering (cs.SE) ; Performance (cs.PF). Pagina del lavoro: https://arxiv.org/abs/2608.19520 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-10-18T11:39:59.162Z dalla pagina https://arxiv.org/catchup/cs.PF/2026-08-21?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).