Android Benchmarking and other stories
summary
Covers using Android Profiler plus Google libraries microbenchmark and macrobenchmark to measure CPU, frames and startup times (examples: sorting 10,000 items, RecyclerView scrolling), and the new in‑app junkstats to flag slow frames; benchmarks emit JSON with min/median/max (examples show runs around 651–749 ms variance) and require real devices or Firebase Test Lab. CI workflow installs APKs, runs benchmarks, stores build→time pairs, and detects regressions with a step‑fitting algorithm (sliding window) instead of naïve thresholds.
AI-written summary · about
chapters (11)
- 0:00Introduction and speakers
- 1:17What is benchmarking
- 3:00Android Profiler overview
- 5:49Microbenchmark framework
- 9:21Macrobenchmark framework
- 13:18JankStats framework
- 16:48Detecting regressions in CI
- 20:01App startup time example
- 25:46Step fitting algorithm
- 29:18Recap and resources
- 31:03Q&A and closing
related talks
33mAndroid Benchmarking and other stories
40mMonitor App performance using Jetpack Benchmark
20mMeasure What Matters with Jetpack Benchmark (Lightning)
37mImproving app performance with benchmarking
34mPerformance in a Kotlin world
43mExperiments for your Android builds driven by Gradle Profiler
29mWhat's new in app performance
40mMy Journey: Adding Baseline Profiles to a Production-Based Android App: Success or Failure?
