~/talk

"10 performance sins of Rails applications"

Talkat RubyC 2019 · 2019-09-14..09-15· [ruby-on-rails, web-performance]
links:none on file
slides:none on file

Shows specific fixes and measured results: set up New Relic/Skylight/Datadog and track mean, median and 95th percentile; move a preloaded 2000 stations live-search from front end to backend and cut initial page load ~20% with a ~3% conversion lift; removing one unnecessary Facebook Pixel yields ~50% speed increase; use pluck/select/count and add DB indexes to avoid heavy ActiveRecord objects; push email/report work to background using Active Job / Sidekiq and enqueue IDs not objects; test on slow phones to catch front-end bloat.

AI-written summary · about

  1. 0:00Introduction
  2. 1:36Measuring performance is key
  3. 7:04Front-end vs back-end speed
  4. 11:08Optimization without measurement
  5. 15:34Doing too much in code
  6. 18:45Caching strategies in Rails
  7. 20:13Active Record performance pitfalls
  8. 27:12Offload work to background jobs
  9. 31:40Front-end performance matters
  10. 34:00Q&A and closing
~/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.