Panel - Performance
summary
Panel lists concrete signals and fixes: check Chrome/Safari memory panel and look for leaks from long-lived subscriptions or sloppy useEffect cleanup; WebAssembly can exhaust its linear memory. Optimistic updates cause recurring bugs so teams sometimes disable optimistic updates in Apollo until behavior is audited. Heavy DOM from tens of thousands of nodes moves work to workers with WebGL/canvas or WASM rendering, sped up by a prefetch link for workers and message-passing patterns like unsubscribe in useEffect or rxjs for state. Small refactors that buy ~5% are often not worth it.
AI-written summary · about
chapters (6)
- 0:00Memory optimization challenges
- 4:24Optimistic rendering pitfalls
- 9:20Optimization backfires and architecture
- 12:11Worker architectures and debugging
- 15:00Start performance optimization
- 19:53Finnish React community and closing
related talks
58mPanel 3: Performance
29mParallel computing in ReactJS: Provide a pleasant user experience
33mPanel debate: Day 1
01h 08mSquashing JavaScript Bugs
34mOptimizing Performance in Large-Scale React & Node.js Applications
29mWatch your back, Browser! You're being observed
17mSupercharging React Performance with JavaScript Signal Optimisation
19mLet the Main Thread Breathe!