Finding and Fixing Performance Problems
summary
Uses real Play Store profiling and shows concrete wins not vague theory: finds UI thread pauses up to ~300 ms caused by heavy inflation and many views, reports 450 visible views / 722 instantiated views (sometimes thousands cached), exposes costly uploads like 12 ms+ texture uploads for large bitmaps (e.g. 1080×500), and traces overdraw and alpha costs with systrace and GFX info. Demos Android Studio profiler, Hierarchy Viewer, meminfo, and FrameMetricsAggregator and shows where to fix actual hotspots.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:31A Random App
- 4:07Overdraw
- 9:37hierarchyviewer
- 12:51adb shell dumpsys gfxinfo
- 17:36adb shell dumpsys meminfo
- 19:30Profile GPU Rendering
- 21:15Android Studio Profilers
- 22:11Android Studio: Memory Profile
- 22:57Android Studio: CPU Profiler
- 41:29framestats
- 43:42Better Yet: FrameMetricsAggregator
related talks
33mUI profiling in examples. Where is my bottleneck?
37mUI profiling in examples. Where is my bottleneck?
35mIn Search of Performance: the Subtle Art of Android Profiling
46mProfiling with Examples: Hunting the Bottleneck
34mPerformance in a Kotlin world
31mImprove app performance with Android Studio Profilers
53mPractical Performance Tuning on Android
43mPerformance in a Kotlin World
