Chrome Internals and Rendering Performance
summary
Covers Chrome’s move from WebKit to the Blink fork, describing a large refactor that replaced Web IDL code and removed legacy pieces while the codebase remains around 6 GB. Explains the rendering pipeline that uses compositor and GPU layers to keep FPS high, and how CSS hints like will-change and position:fixed plus explicit layer promotion trade memory for fewer repaints. Describes Web Animations (and polyfills) and practical debugging tools that expose layers, paint activity, and FPS.
AI-written summary · about
chapters (8)
- 0:00Chrome and WebKit intro
- 5:15Blink creation differences
- 11:43Rendering and process management
- 15:35Compositing and graphics layers
- 22:57Debugging composite layers
- 27:58Mobile and GPU optimization
- 31:59CSS vs JavaScript animations
- 35:43Q&A
related talks
39mFrom code to pixels in a Blink
37mRendering performance inside out
44mWe Are All Good with Browsers Made by Others
31mJank Busters - Chrome Rendering Performance
41mBrowser Internals for JS Devs
58mUntangling Browser Threads
45mThe Browser Is Not a Flux Capacitor, and You Know It... Or Do You?
40mWhat’s New with Chrome and the Web