Optimizing Android Build Performance

on YouTube ↗48m

" summary

Twitter instruments Android Studio 3.0 and Gradle features to cut build time: enable the Gradle daemon, use the build cache (local + CI remote) and incremental compilation with the Java library plugin, and profile with build scans and YourKit. Modularization grows from 54 to 115 modules and clean builds fall from ~5m to ~2.5m while incremental builds hit 13 seconds. Fixes raise remote cache hit rate from 70%→80%; annotation processors and absolute paths remain common cache killers.

AI-written summary · about

" chapters (10)

1. 0:00Introduction and speakers
2. 2:46Build performance challenges
3. 8:24Gradle build improvements
4. 11:11Build cache and parallelism
5. 17:32Tools for understanding builds
6. 22:31Debugging build issues
7. 38:03Debugging Gradle and AGP
8. 41:57Optimizing build parallelism
9. 43:02Twitter build results and future work
10. 46:59Q&A

" related talks

• 30mImproving Android Build performanceTony Robalik · droidCon NYC 2018
• 40mImproving Android Build PerformanceVolker Leck · droidCon Berlin 2019
• 31mImproving Android Build performanceTony Robalik · droidcon San Francisco 2018
• 33mIMPROVING ANDROID BUILD PERFORMANCEStefan Oehme · droidcon Berlin 2018
• 40mMake The Android Gradle Plugin Work For YouAdarsh Fernando, Izabela Orlowska, Amr Affify, Maksim Lazebnik · droidcon London 2019
• 27mFaster builds on Android: from 2 minutes to 2 secondsPhilipp Hofmann · droidcon Italy 2019
• 30mHow we brought down our build times. General optimization tipsManuel Nakamurakare · droidcon San Francisco 2022
• 34mWhat's new in Android development toolsJamal Eason, Tor Norbye · Google I/O 2022