~/talk

UI profiling in examples. Where is my bottleneck?

Talkat Mobilization 8 · on Friday, 2018-10-26· [android]
links:none on file
slides:none on file

Walks through concrete tooling and fixes: use dumpsys gfxinfo, GPU profiler and Systrace to get fps and janky-frame counts, export view layers with HierarchyViewer or Scalpel to find overdraw, and read Android Vitals for fleet metrics. Explains Android render pipeline (DisplayLists, Choreographer, Render Thread) and the 60 FPS / 16 ms budget. Shows real wins: a controller-stack bug inflates view count from ~300 causing 40ms renders reduced to 6ms after fix, and an EditText cursor bug causing ~20ms jank.

AI-written summary · about

  1. 0:00Introduction to UI profiling
  2. 8:11Detecting UI performance issues
  3. 11:23Common UI bottlenecks
  4. 14:13Debugging layout complexity
  5. 18:07Using ViewStub for optimization
  6. 21:40Hierarchy Viewer limitations
  7. 22:01Fixing overdraw problems
  8. 25:35Real-world performance testing
  9. 26:38Analyzing frame drops
  10. 27:42Prioritizing UI optimizations
  11. 30:51Automating performance checks
  12. 31:52Handling slow devices
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.