The future of the browser
summary
Browsers must get faster by embracing parallelism: coarse-grained multi-process tabs and fine-grained parallelism across cores. Claim: splitting CSS and layout work speeds pages proportionally to CPU cores. Tools actually used: Rust to eliminate data races, Servo experiments, pieces imported into Firefox as Stylo and WebRender under Project Quantum. Numbers: 60fps needs ~16ms, new iPad 120fps ~8ms, VR ~90fps and ~16.5 million pixels. Result: measurable speedups and smoother animations; WebAssembly and web workers add parallelism for application code.
AI-written summary · about
chapters (9)
- 0:00The browser performance gap
- 5:52The web rendering pipeline
- 12:04Painting and compositing
- 14:44Multi-process architecture
- 17:13From Moore's Law to cores
- 20:17Coarse-grained parallelism
- 25:17Fine-grained parallelism
- 29:24Quantum and WebRender
- 31:37The future of the web
related talks
31mThe parallel future of the browser (Closing Keynote)
03mThe parallel future of the browser
28mToday: Making a browser fast, the story of Firefox Quantum.
44mWe Are All Good with Browsers Made by Others
33mWe are all good with browsers made by others
13mlightning talk
43mMaximum performance in web browsers
51mBenchmarking Browsers