Squeezing the last drop of performance out of your Gradle builds (en)
summary
Measurements show configuration overhead falls from 4.3s to 0.9s by enabling configure-on-demand and the Gradle daemon and updating to newer Gradle (2.8+); use the dry-run and --profile flags to find hotspots. Use Java 1.8, SSDs, avoid dynamic dependencies and expensive work during configuration. For large apps, pre-dex libraries and set minSdk 21 for native multidex to cut a 50s build to ~18s; try continuous builds, parallel project config or alternative tools (Buck) for bigger wins.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:15Gradle Build Lifecycle
- 4:44Configure on Demand
- 5:57Gradle Daemon
- 7:33Gradle Version
- 9:33JVM Version
- 11:36Avoid Heavy Computation
- 13:16Dependencies
- 15:36Continuous Builds
- 17:56Task Graph
- 23:06Build Breakdown - Iosched
- 24:40Changing Values
- 26:39The Dexer
- 28:01The minSdk 21 Trick
- 30:38Really Large Projects
- 32:10Utilizing Predexing
- 33:20Multi-Project Builds
- 34:34Parallel Task Execution
- 35:51Incremental Javac
- 37:10The Future Looks Brighter
- 38:05Alternative Build Systems
- 39:02JRebel for Android
related talks
28mMaking the most of your Gradle Builds
33mIMPROVING ANDROID BUILD PERFORMANCE
01h 01mImprove Java build performance with Gradle 5
40mImproving Android Build Performance
31mImproving Android Build performance
49mGradle
55mMake Your Build Great Again
27mFaster builds on Android: from 2 minutes to 2 seconds