Apache's mod_proxy_balancer module is a fully blocking module and with the default httpd.conf you're going to max out in the 120-160 requests/ second range on a decent box. You can tune up its proxying to about a 1000 req/sec
So yes the net result is that you can really only put a couple of mongrels behind apache's proxy engine (about 2 "hello world" rails mongrels). If you can hit mongrels directly and all is fine, but it's clogged up via apache ( and you're doing in the hundreds of request/sec), than this is the botteneck that you've hit. This at least explains the original poster's problem. -Jason On Sep 15, 2007, at 6:05 AM, "Ben Kruger" <[EMAIL PROTECTED]> wrote: > We are having a similar problem. For the last 6 months everything > has been fine. The last couple of weeks as our pageviews continue > to rise we are now facing an unresponsive Mongrel intermittently. > > We are running on BSD 6.2 with 4 Mongrels in the cluster. > > Comments are appreciated as well! > > Thank you, > > Ben > _______________________________________________ > Mongrel-users mailing list > Mongrel-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
