Experiments for your Android Builds Driven
summary
Uses Gradle Profiler to run reproducible scenarios (example: 2 warmups + 5 measured builds or 4 warmups + 15 measured builds), outputting CSV and HTML reports with means, percentiles and standard deviations. Compares two branches (example JDK8 vs JDK11) using a left-tailed paired t-test (student t) to compute a p value and decide significance (example p ≈ 0 for a clear speedup). Notes automation via CI is possible but slow, and Docker or offline/build-cache flags help isolate environment.
AI-written summary · about
chapters (9)
- 0:00Introduction to Gradle Profiler
- 10:02Measuring Gradle builds with Profiler
- 14:23Evaluating benchmark results
- 17:35Statistics for build improvements
- 21:05Hypothesis testing explained
- 29:16P-value and statistical significance
- 31:22Automating experiment analysis
- 34:18Real-world benchmark examples
- 37:56Final remarks and Q&A
related talks
43mExperiments for your Android builds driven by Gradle Profiler
44mA Healthy Dose of Gradle
37mThe Build Shrugged
40mImproving Android Build Performance
37mBecoming and Staying a Productive Developer with Build Scans, Build Validation Scripts and Gradle
36mKeeping your team’s Gradle builds in top shape
37mBuild bigger, better: Gradle for large projects
33mIMPROVING ANDROID BUILD PERFORMANCE
