IMPROVING ANDROID BUILD PERFORMANCE
summary
Shows how to find and fix the real slow spots: run build scans and the Gradle profiler to see configuration vs execution time, GC, and per-plugin costs; flag rules like >10 ms configuration per project, examples of 30 s config for 50 projects and builds with 400 variants. Fixes include deferring dependency resolution to execution, removing Crashlytics’ debug timestamp that forces full rebuilds, using the Gradle Build Cache (300 downstream builds pull cached artifacts), enabling -Dorg.gradle.parallel, and opting processors into Gradle 4.7 incremental annotation processing.
AI-written summary · about
chapters (7)
- 0:00Introduction to build performance
- 2:10Tools and profiling process
- 9:19Configuration time issues
- 16:47Execution time bottlenecks
- 23:28Build caching and parallelism
- 26:47Monitoring and long-term tracking
- 30:24Resources and closing
related talks
40mImproving Android Build Performance
31mImproving Android Build performance
30mImproving Android Build performance
28mMaking the most of your Gradle Builds
36mTop Build Performance issues in Android projects - 2023 Edition
27mFaster builds on Android: from 2 minutes to 2 seconds
36mImproving Gradle Builds
47mBuild times breaking your flow? Learn how to speed them up!
