Thanks, Eric. Great plugin!
On Mar 5, 2007, at 5:17 PM, Eric Anderson wrote: > Henry Poydar wrote: >> only fired on start up. I'm going to investigate further with the >> general assumption that the Engine plugin is not the bottleneck. > > Something I have found to be VERY useful at debugging performance > problems in Rails is: > > http://revolutiononrails.blogspot.com/2007/01/plugin-release- > browser-profiler.html > > It uses ruby-prof (the ruby profiler written in C for fast results) to > profile your request. Simply append a querystring param and you get > all > the gory details. It takes a bit of understand the results that > ruby-prof outputs (it's not like any profiler I have used) but once > you > understand it you can find the exact place where the performance > problems exist. > > Much more fine grain than Rails' 90% render, 10% database. :) > > Eric > > _______________________________________________ > engine-users mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-users-rails- > engines.org _______________________________________________ engine-users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
