gradle-build-performance

Caches configuration phase across builds (AGP 8.0+): Reuses task outputs across builds and machines: Build independent modules simultaneously: Allocate more memory for large projects: Reduces R class size and compilation (AGP 8.0+ default): KSP is 2x faster than kapt for Kotlin: Pin dependency versions: Put most-used repositories first: Composite builds are faster than project() for large monorepos: Don't read files or make network calls during configuration: Avoid create() , use register() : Symptoms : Build scan shows long "Configuring build" time Causes & Fixes : Symptoms : :app:compileDebugKotlin takes too long Causes & Fixes : Symptoms : Tasks always rerun despite no changes Causes & Fixes : For advanced build analytics: After optimizations, verify: - Build times are slow (clean or incremental) - Investigating build performance regressions - Analyzing Gradle Build Scans - Identifying configuration vs execution bottlenecks - Optimizing CI/CD build times - Enabling Gradle Configuration Cache - Reducing unnecessary recompilation - Debugging kapt/KSP annotation processing - "My builds are slow, how can I speed them up?" - "How do I analyze a Gradle build scan?" - "Why is configuration taking so long?" - "Why does my project always recompile everything?" - "How do I enable configuration cache?" - "Why is kapt so slow?" - Measure Baseline — Clean build + incremental build times...