Accurately measure app performance with profileable builds
summary
Debuggable builds turn off compiler optimizations and inflate UI jank, so timing on debug can be far off; using the profileable tag on Android 10+ lets profilers sample call stacks and system traces with minimal overhead and near-release timing accuracy. Android Studio Flamingo with Android Studio Flamingo and AGP 8.0 adds a profile with low overhead option that builds a profileable release, or add the manifest flag, use a non‑debuggable build and a signing key to profile manually.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:23Overview of profiling
- 0:51Profiling the debug build
- 2:21Introducing profileable
- 3:30How to automatically enable profileable
- 4:23How to manually enable profileable
- 5:51Summary
related talks
35mIn Search of Performance: the Subtle Art of Android Profiling
24mPerformance Tooling
36mActionable App Performance Measurement
40mDebugging Android Performance at Scale: Lessons from Building Datadog's Mobile Profiler
13mAndroid Studio Profiling
41mDeep dive into Android Studio Profilers
27mSqueezing out the last 5% of performance: AGDE, profile-guided optimization, and automation
39mAndroid App Performance in a Nutshell
