GPU. The journey from code to pixel
summary
Explains how Android turns view code into pixels by tracing the pipeline: CPU measures/layouts/draws, GPU renders, and the system must finish each frame within 60 FPS = 16ms per frame. Covers double buffering and the render thread choreography, common causes of jank like expensive onDraw work, excessive invalidates, and overdraw; shows detection via Show GPU overdraw and GPU profile bars in Developer Options, plus Layout Inspector/Android Studio and Play Console Vitals for device-wide metrics. Practical fixes include clipRect/quickReject and offloading heavy work.
AI-written summary · about
chapters (39)
- 0:00Introduction
- 0:18Chet Haase
- 1:05Yonatan Levin
- 3:37Why do we love apps
- 4:53Motion is key
- 5:17How is motion perceived
- 6:25FPS
- 8:53Frame rate
- 9:18Reallife examples
- 11:30Our problem
- 11:55What do we do
- 13:57What went wrong
- 16:20What happens in games
- 17:15Performance issues
- 18:03Remember Fat
- 20:31Layout Editor
- 20:59View is build
- 22:48Overdraw
- 23:51Example
- 24:17Chuck Norris
- 24:30What does blue mean
- 25:10What does red mean
- 25:22Looking at your code
- 25:36Walking us through your code
- 25:51Unnecessary backgrounds
- 26:53Quickly reject a view
- 27:12Clipper Jack
- 27:45GPU Profiling
- 28:13Strain as Bars
- 29:14Explanation
- 30:03Choreography
- 31:36Animations
- 31:56Extensive calculations
- 32:35DRO
- 32:50Singing upload
- 33:59Buffers
- 34:36Measure Layout
- 34:56Vitals Dashboard
- 35:32Vitals
