Improving Android Build performance

on YouTube ↗31m

" summary

Uses real Chess.com builds and the Gradle profiler to measure scenarios, finds GC as high as 17s (8% of build), and shows upgrading Gradle/AGP and enabling the daemon cuts startup time. Demonstrates fixes: stop resolving dependencies during configuration, lazy task registration, move git/version work to the root to avoid repeated work, and pin Crashlytics ID to shave ~20s. Shows KAPT raising a 30s clean build to 50s, benefits of build scans, remote cache and parallel builds across 16 modules, and the new incremental annotation processing support.

AI-written summary · about

" chapters (16)

1. 0:00Introduction and setup
2. 1:12Scientific method for profiling
3. 2:55JVM tuning and build scans
4. 4:59Build scan creation and benefits
5. 6:23Startup and configuration time
6. 9:51Avoiding task configuration
7. 13:02Build logic and build source
8. 14:26Execution time and incremental builds
9. 17:15Compile avoidance and modularization
10. 19:41Annotation processors and INCAP
11. 21:29Caching and build cache
12. 23:54Remote caching benefits
13. 24:15Parallelism and task execution
14. 26:02Gradle Enterprise for monitoring
15. 28:31Resources and closing remarks
16. 29:14Q&A session

" related talks

• 30mImproving Android Build performanceTony Robalik · droidCon NYC 2018
• 33mIMPROVING ANDROID BUILD PERFORMANCEStefan Oehme · droidcon Berlin 2018
• 48mOptimizing Android Build PerformanceHans Dockter, César Puerta · droidcon San Francisco 2017
• 27mFaster builds on Android: from 2 minutes to 2 secondsPhilipp Hofmann · droidcon Italy 2019
• 36mTop Build Performance issues in Android projects - 2023 EditionNelson Osacky, Inaki Villar · droidcon New York 2023
• 30mHow we brought down our build times. General optimization tipsManuel Nakamurakare · droidcon San Francisco 2022
• 28mMaking the most of your Gradle BuildsEgor Andreevici · Droidcon Italy 2017
• 19mCOMPILING...? HOW TO REDUCE YOUR WAIT TIMES AND "GET BACK TO WORK"Paul Davies · droidcon Berlin 2018