Table and Collection Views Optimization
summary
Claim: replace many subviews with a single drawn view to shift work from the GPU to the CPU. Implementation uses override drawRect and drawInRect with Core Graphics and flatten the view hierarchy, measured with the Core Animation instrument on device. Results: on an iPad 2 the traditional approach plateaus around 27 fps vs optimized ~45 fps, with a noticeable gap by ~500 cells; Interface Builder/Auto Layout performs worse, dropping toward ~20–22 fps.
AI-written summary · about
chapters (6)
- 0:00Start
- 4:16Practical example
- 4:45Traditional approach
- 5:06Less work for the GPU
- 6:10How to reasure frame rate
- 7:45Autofayout?
related talks
13mImproving Scrolling Performance through GPU Optimisation
54m60 fps UI on iOS
37mFrom View to Pixel
22mTaming a Four-Year-Old Detail Screen That Slowed Down Over Time
38mBuilding Responsive Interactions
23mUnderstanding Render Loop to optimise SwiftUI
24mSwiftUI Performance Tips
18mThe Amazing Race; Performance of Standard iOS Elements & Tech
