On Nov 26, 2007 12:59 PM, Bob Br <[EMAIL PROTECTED]> wrote: > I'm starting to benchmark my application and was wondering if this is > normal results / degradation when new layers are added.
Yup. There is quite a bit of Ruby executed per request, and Ruby is a slow language. By the time you add a real application, though (with typical round-trips of 20-50 msec), all this overhead becomes something like ~10-20% of your total CPU time, so it's not really a big deal. > Can anyone suggest either some config settings, or where to look to see what > improvements can be made? Two common pitfalls that make a big difference in the tests of [render :text => 'Hello, World'] variety are: * running Rails in development environment (forgetting to run Rails with -e production ) * storing sessions on file system (use database or memcached instead, or turn sessions off altogether) -- Alexey Verkhovsky CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] RubyWorks [http://rubyworks.thoughtworks.com] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
