Search papers, labs, and topics across Lattice.
This study evaluates the energy consumption and performance of three Java garbage collectors鈥擲erial, Parallel, and G1鈥攁cross varying workloads and JDK distributions. The findings reveal that while Parallel collector achieved the lowest mean energy consumption, no statistically significant differences were found among the collectors, emphasizing that workload intensity is a more critical factor influencing energy use. Consequently, the research suggests that garbage collector selection should be tailored to specific applications rather than relying on generalized rankings.
Workload intensity, not garbage collector choice, is the key driver of energy consumption in Java applications, challenging conventional wisdom about collector rankings.
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.
