What to do when Mongrel stops responding...
summary
When Mongrel stops responding the actionable steps are: attach with GDB with Ruby macros to get C and Ruby stack traces and even evaluate Ruby in-process (note: GDB freezes the process), run lsof to see file locks, and use DTrace probes to trace syscalls plus Ruby-level events without heavy overhead. A small shim called x-ray fires Ruby probes portably so requests, rendering and DB times are aggregated; demos show consistent sub-100ms actions vs sporadic multi-second outliers, and the tooling reliably isolates syscall vs app-level causes.
AI-written summary · about
chapters (6)
- 0:00Start
- 9:33Use Gdb To Attach to the Process
- 15:09How Can We Get the Macros
- 27:38Dtrace for Performance Analysis
- 50:11Build Own Custom Instruments
- 50:44What Should You Remember about this Presentation
