React Component Profiling
summary
War story of shaving a page from 3.4s to 140ms: uses the Chrome React Profiler to find three real culprits — a 10MB Date‑holidays library replaced by a 73‑line implementation (saved ~1s), nested loops over a full Redux store that were restricted to needed items, and costly per‑button session lookups fixed with simple caching — then applied reselect + useMemo + memo to cache per‑month computations and component output, yielding consistent ~140ms renders.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:06React Profiler basics
- 3:34Flame graph vs ranked display
- 4:16Fixing invoice list bottleneck
- 5:41Nested loops performance issue
- 6:25Project months performance problem
- 7:50Caching with Reselect and memo
- 11:00Memoizing collapsed project months
- 12:45Final performance results
- 13:51Key takeaways
- 14:32Profiler alternatives
related talks
40mProfiling React rendering performance
27mProfiling and Optimizing Performance of React Applications
28mDemystifying React Performance
38mLive Coding - Optimizing a React application
20mPerformance Anxiety with React: Track and increase speed of your apps
11mMaximizing React Perfomance with DevTools: Profiler and Components
51mTips and tricks for optimizing your React application
55mUnderstanding Performance of React Applications
