~/talk

Building RailsPerf, a toolkit to detect performance regressions

Talkat RailsConf 2015 · 2015-04-21..04-23· [ruby-on-rails, observability]
slides:none on file

Practical account of building RailsPerf: a per-commit regression detector that runs per-commit benchmarking against Rails using a suite of microbenchmarks (ActiveRecord, ActionController, router, views), measuring timings and allocations, isolating runs with docker isolation, and posting results back to GitHub. Prototype embeds into ruby-bench, runs on dedicated hardware, has ~10–20 Rails benchmarks, contributes to ~250k builds, and already identifies regressions that get fixed the next day. The repo, CI flow, and visualization are all implemented.

AI-written summary · about

  1. 0:00Start
  2. 0:12Building a toolkit to detect performance regressions in Ruby on Rails core
  3. 0:47Catching Performance Regressions in Rails
  4. 1:27What's a performance regression?
  5. 1:46What's a performance regression in Rails?
  6. 2:16Case Study
  7. 2:33Discourse
  8. 3:53Faster framework = Faster app
  9. 4:23Examples from Rails commits
  10. 4:35Metrics
  11. 5:36Basic primitives
  12. 11:54Optimize only "hot" code
  13. 12:46The Idea to build a service
  14. 16:57Correct benchmarks
  15. 19:00The Service
  16. 24:28250k builds for Ruby
~/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.