~/talk

IMPROVING ANDROID BUILD PERFORMANCE

Talkat droidcon Berlin 2018 · 2018-06-25..06-27· [devops-and-delivery, android]
links:none on file
slides:none on file

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

  1. 0:00Introduction to build performance
  2. 2:10Tools and profiling process
  3. 9:19Configuration time issues
  4. 16:47Execution time bottlenecks
  5. 23:28Build caching and parallelism
  6. 26:47Monitoring and long-term tracking
  7. 30:24Resources and closing
~/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.