On Mar 26, 2009, at 12:32 PM, Scott Kulik wrote: > I have a page that does a lot of calculations...that for some reason > takes 19 seconds to load when running in my development environment. > > Looking at my logs I can see Rendering took .8 seconds and the DB took > 2.38 seconds: > > Completed in 19.81708 (0 reqs/sec) | Rendering: 0.80910 (4%) | DB: > 2.38379 (12%) | 200 OK [http://wldev.kuliksco.com/compounds] > > where is the rest of the time coming from? is this time when the > cpu is > chugging away doing calculations? I don't think it would be a > bandwidth > issue since I'm testing from the same router/subnet. > --
Yes, the remaining 16.62419 seconds are your code heating up the CPU. (Of course, not all of what falls outside of Rendering and DB is necessarily code written by you, but you'd have to instrument your code to find out more details.) You can try New Relic's Rails Performance Monitor [1] to find out some of those details. [1] http://newrelic.com/get-RPM.html -Rob Rob Biedenharn http://agileconsultingllc.com [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
