~/talk

Rails Performance First Aid

links:none on file
slides:none on file

Shows concrete fixes: use New Relic or Skylight and flamegraph profilers to find hot spots (one app drops from 6 seconds to ~500 ms after fixes), run load tests before/after, and aim for ~250–300 ms end-to-end. Remove Ruby-level work by adding joins or SQL NOT EXISTS queries, fix N+1s with Bullet and the undocumented preloader trick, add partial indexes and EXPLAIN plans, move servers closer to users to cut network latency, and use fragment/JSON caching with Redis and conditional GETs (304s).

AI-written summary · about

  1. 0:00Introduction
  2. 1:03Rails performance myths
  3. 5:04First aid approach
  4. 11:16Measuring performance
  5. 16:57Database tuning basics
  6. 25:30Caching strategies
  7. 28:37Quick optimizations
  8. 30:06Summary and Q&A
~/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.