Improving Android Build performance
summary
Typical installs see huge wins by measuring first: use Gradle Profiler to script repeatable scenarios and build scans to find the exact task that regresses. Upgrading to recent Gradle and the Android plugin plus a healthy daemon cuts GC stalls (example: 17s GC = 8% of build time). KAPT can add tens of seconds (a Kotlin AP example: clean 30s → +50s with KAPT), enabling incremental annotation processing (Gradle 4.7 opt‑in) and using the build cache / remote cache and parallel execution often reduces team build time by orders of magnitude.
AI-written summary · about
chapters (13)
- 0:00Why build performance matters
- 1:09Scientific approach to profiling
- 3:13Update tools and JVM tuning
- 4:58Using build scans for debugging
- 7:26Optimizing Gradle daemon startup
- 8:52Reducing configuration time
- 13:02Structuring build logic
- 14:45Execution time and incremental builds
- 17:12Faster compilation techniques
- 21:27Build caching benefits
- 23:34Parallel task execution
- 26:03Monitoring builds with Gradle Enterprise
- 28:12Key takeaways and resources
related talks
31mImproving Android Build performance
40mImproving Android Build Performance
33mIMPROVING ANDROID BUILD PERFORMANCE
27mFaster builds on Android: from 2 minutes to 2 seconds
48mOptimizing Android Build Performance
40mMake The Android Gradle Plugin Work For You
30mHow we brought down our build times. General optimization tips
32mFaster Feedback Cut Gradle Build and Pipeline Times in Half
