~/talk

Improving Android Build performance

Talkat droidCon NYC 2018 · 2018-08-27..08-28· [devops-and-delivery, android]
links:none on file
slides:none on file

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

  1. 0:00Why build performance matters
  2. 1:09Scientific approach to profiling
  3. 3:13Update tools and JVM tuning
  4. 4:58Using build scans for debugging
  5. 7:26Optimizing Gradle daemon startup
  6. 8:52Reducing configuration time
  7. 13:02Structuring build logic
  8. 14:45Execution time and incremental builds
  9. 17:12Faster compilation techniques
  10. 21:27Build caching benefits
  11. 23:34Parallel task execution
  12. 26:03Monitoring builds with Gradle Enterprise
  13. 28:12Key takeaways and resources
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.