In production mode, the first time your app is accessed on each
instance of mongrel, mongrel loads all the ruby classes it needs (it
loads them EVERY time in development). The load is what's slowing down
the initial hit to each mongrel. After that, the classes are present
in memory, thus fast hits.

-C

On Mar 6, 6:38 am, "Alexey Verkhovsky" <[EMAIL PROTECTED]>
wrote:
> On 3/6/07, Al Evans <[EMAIL PROTECTED]> wrote:
>
>
>
> > Any chance you're low on memory and your mongrel process(es) are getting
> > swapped out?
>
> This would be my second guess, too.
>
> Alex


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to