On Wed, Sep 1, 2010 at 3:46 PM, Travis Whitton wrote:
> Pretty sure we're hitting up against a concurrency problem. I can
> reproduce the issue on a machine that's not in production with very
> similar specs by running ab (apache bench) on three hefty client
> machines with concurrency set to 1,00
Pretty sure we're hitting up against a concurrency problem. I can
reproduce the issue on a machine that's not in production with very
similar specs by running ab (apache bench) on three hefty client
machines with concurrency set to 1,000 on each machine. Doing some
tests serving static content, I c
On 31.08.2010 23:38, Eric Covener wrote:
Running `netstat -tapn | grep 80 | wc -l' shows 11299
connections to port 80. We're setup to use prefork with the following
configuration.
MaxClients1000
Is the netstat output a typo? With MaxClients 1000 and the default
ListenBackLog of ~500,
> Running `netstat -tapn | grep 80 | wc -l' shows 11299
> connections to port 80. We're setup to use prefork with the following
> configuration.
>
> MaxClients 1000
Is the netstat output a typo? With MaxClients 1000 and the default
ListenBackLog of ~500, you should have started refusing co
Hi there, we're having a strange issue and wondering if anyone might
have any suggestions. We have a cluster of apache machines and are
experiencing a problem where the load average and other hardware
metrics are well below normal ranges, but the response times are
exceedingly high (even for tiny p
