Several components are rendering
summary
Slack desktop suffers systemic re-renders from a Redux+React architecture so the client performance team builds observability, surfaces input delay key press lag as a KR-level metric, and finds >50% of frames miss the 16ms budget with P99 pauses over 200ms. Engineers get lint guard rails, hooks and small fixes in a toolbox, plus a finer-grain subscription layer that yields a 30% improvement in Redux loop times — a pragmatic fix that measurably reduces jank.
AI-written summary · about
chapters (13)
- 0:00Introduction and context
- 2:04Slack as a desktop app
- 3:36Browser rendering mechanics
- 5:04Defining performance goals
- 7:16From regression to metrics
- 9:16Establishing performance KRs
- 10:47Deep dive into React and Redux
- 13:23Bottlenecks at scale
- 14:28Architectural decision making
- 17:27Building a performance culture
- 19:33Tooling and guardrails
- 21:31Program impact and results
- 22:41Reflections on the journey
related talks
47mReact, Rendering, Performance
16mPerformance in React and Next.js
34mOptimizing Performance in Large-Scale React & Node.js Applications
25mPerformance Without Compromise
02h 50mReact: Internals and Advanced Performance Patterns
30mConcurrent Rendering in React
27mDeep diving on Concurrent React
42mConcurrent Rendering in React