Panel Discusion - Performance problems in Rails applications
summary
Benchmarks show ActionView plus partials can dominate render cost — pulling one row into a partial made an index view 40% slower. Common mistakes: loading big collections into memory instead of using find_each vs each, serializing huge objects into background jobs that become slower than DB queries, and leaving DB connections open while calling external services — fix by close DB connection before external calls. Use OpenTelemetry/Honeycomb/CloudWatch, PG analyzer, profilers and pragmatic timeboxed exploration, indexing, pagination or Elasticsearch where needed.
AI-written summary · about
related talks
25mPowerful Data: Making Rails Apps Faster with Aggregation
01h 02mPerformance
26mRails Performance Monitoring 101: A Primer for Developers
35m"10 performance sins of Rails applications"
54mThe View is Clear From Here
44m"The View Is Clear from Here"
30mRails Performance monitoring: A primer for developers
42mRender It! A Deep Dive into ActionView and Template Engines