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.
on 2009-03-26 17:32
on 2009-03-26 18:08
On Mar 26, 2009, at 12:32 PM, Scott Kulik wrote: > 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  to find out some of those details.  http://newrelic.com/get-RPM.html -Rob Rob Biedenharn http://agileconsultingllc.com Rob@AgileConsultingLLC.com
on 2009-03-26 20:37
Rob Biedenharn wrote: > You can try New Relic's Rails Performance Monitor  to find out some > of those details. > >  http://newrelic.com/get-RPM.html > > -Rob > > Rob Biedenharn http://agileconsultingllc.com > Rob@AgileConsultingLLC.com thanks rob! i just installed the plugin and I can see where all the cpu is going.
on 2009-03-26 20:55
And where was it going? ;-) dwh
on 2009-03-27 22:06
Denis Haskin wrote: > And where was it going? ;-) > > dwh i had some cpu intensive code to validate the items on the page and i screwed up the query so it was running the code on all 7000 rows in the table instead of just the 50 displayed on current page. doh!