On Wed, Mar 07, 2007 at 12:55:06AM -0600, Alexey Verkhovsky wrote: > This is exactly what Mongrel does when it cannot cope with the incoming > traffic. I've discovered the same effect today. > > You are definitely overloading it with 80 requests per second. After all, > it's a single-threaded instance of a fairly CPU-heavy framework. With no > page caching it should cope with ~10 to 30 requests per second max. > > The crappy part about this, after the overload condition is off, the Mongrel > process stays at 150Mb. Not a problem when you are hosting one app on the > box, but becomes a problem when it's ten.
I've had some success reducing the number of processors. Try reducing this somewhat and see if it helps. -- Cheers, - Jacob Atzen _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
