~/talk

React Component Profiling

Talkat React Brussels 2023 · on Friday, 2023-10-13· [react, web-performance]
links:none on file
slides:none on file

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

  1. 0:00Introduction
  2. 1:06React Profiler basics
  3. 3:34Flame graph vs ranked display
  4. 4:16Fixing invoice list bottleneck
  5. 5:41Nested loops performance issue
  6. 6:25Project months performance problem
  7. 7:50Caching with Reselect and memo
  8. 11:00Memoizing collapsed project months
  9. 12:45Final performance results
  10. 13:51Key takeaways
  11. 14:32Profiler alternatives
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.