Here are the ones I tried. Hope the comments aren’t too confusing
- Simple Rails Log Query Analyzer
- Ran
ruby bin/query_log_analyzer.rb ../log/production.logproduction.log.1 (small log file ~25MB)Just printed the “Totals” heading with no resultsproduction.log (large log file ~400MB)Ran for a long time and nothing happened
- Ran
- The Action Profiler lets you profile actions to determine points of optimization.
- See attachment for the error when running
action_profiler ChartController#index - Madhu thinks it requires Production Log Analyzer (which requires SyslogLogger)
- See attachment for the error when running
rawk.rb
(recommended by Railscast.com)production.log.1 (small log file ~25MB)shows 21,300 requestsproduction.log (large log file ~400MB)—shows only 27,200 requests- Both took about a miute to scan and since only 7,000 difference in requests, we think Rawk is not working
- 07/23/08: Tried
ruby rawk.rb ../log/production.logon sdev but hung for long time and never returned
- Hodel3000CompliantLogger
- Looks like it’s working but requires
mongrel_rails startinstead ofruby script/server. Cannot use it easily with Litespeed probably. - Uses Production Log Analyzer but circumvents SyslogLogger (unlke Action Profiler above)
- Looks like it’s working but requires
- Railscast.com’s Request Profiling
