"Google's Android Runtime (ART) team has achieved a 18% reduction in compile times for Android code without compromising code quality or increasing peak memory usage, delivering significant performance improvements for both just-in-time (JIT) and ahead-of-time (AOT) compilation. As Google software engineers Santiago Aboy Solanes and Vladimír Marko explain, reduced compilation time for JIT-compiled code allows optimization to kick in sooner at runtime, directly improving overall device performance. For both JIT- and AOT-compiled code, faster builds reduce device workload and improve battery life and thermal performance, especially on lower-end hardware."
"Aboy and Marko emphasize the importance of reducing compile times without sacrificing the performance of the generated code or increasing its memory requirements. Typically, they note, making a compiler faster means give something else up. In this case, however: The one resource we were willing to spend was our own development time to dig deep, investigate, and find clever solutions that met these strict criteria. Let's take a closer look at how we work to find areas to improve, as well as finding the right solutions to the various problems."
Android Runtime (ART) reduced compile times by 18% for both JIT and AOT compilation while preserving generated code performance and peak memory usage. Faster JIT compilation allows optimizations to begin sooner at runtime, improving overall device responsiveness. Faster builds for JIT and AOT lower device workload, improving battery life and thermal behavior, especially on lower-end hardware. Measurement relied on pprof to establish baselines and visualize compilation hotspots. A representative mix of first- and third-party apps plus the Android OS were compiled locally to profile workloads. Significant developer time was invested to devise solutions that met strict quality and memory constraints.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]