I'd imagine in the console you are only looking at the model end of the stack. Is the response in the browser have a large volume to return & lots to render? That will easily account for the difference.
On Dec 4, 2009, at 3:07 PM, phil wrote: > What I have done is turned on debugging in a console session on > production and then executed the methods. They are blazing fast - at > least as fast as on dev! Why would executing them via passenger take > so much longer. > > It is a very consistent thing - every request to this certain method > often times out the browser it is so long. Yet... from console it is > fast. What would be different about these two (passenger call vs > console on same box)? > > > On Dec 4, 7:55 pm, Frederick Cheung <[email protected]> > wrote: >> On Dec 4, 6:47 pm, phil <[email protected]> wrote: >> >> >> >>> What can I do to figure out what is going on here? I assume it is >>> perhaps some sort of db locking? But this happens even when no one >>> else is using the production system. >> >> I'd start by looking at the difference between explain statements on >> your local machine and the EC2 instance. If you can narrow it down to >> one particular query that is a lot slower then that would certainly >> help. >> >> Fred >> >> >> >>> All ideas and tips welcomed! > > -- > > 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. > > -- 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.
