Experiments for your Android builds driven by Gradle Profiler
summary
Uses Gradle Profiler to run reproducible benchmarks and saves CSV reports, running 4 warm‑up 15 measure builds per scenario; compares base vs PR with a left‑tailed Student t test and reports p‑value > 0.05 when JDK11 is actually slower so there is no strong evidence of improvement. Also shows a Gradle/tooling bump with p‑value ≈ 0 indicating a real speedup, and publishes a small Python tool (pip) to automate the t‑test.
AI-written summary · about
chapters (15)
- 0:00Intro
- 4:58Measuring Gradle builds
- 7:37Installing Gradle Profiler
- 11:06Demo
- 15:34Scenarios
- 16:36Results
- 20:18Statistical Inference
- 23:39Statistical significance
- 25:10Probability functions
- 26:39Pvalue
- 28:22Tail analysis
- 29:55Parrot test
- 30:44Tools
- 33:16Example
- 38:10Alternative Hypothesis
related talks
33mAndroid Benchmarking and other stories
33mIMPROVING ANDROID BUILD PERFORMANCE
31mImproving Android Build performance
40mImproving Android Build Performance
33mAndroid Benchmarking and other stories
30mImproving Android Build performance
28mMaking the most of your Gradle Builds
43mBenchmarking your application
