Re: AsyncRequestWorkerFactor / Event Sizing / Closing Connections

2012-03-02 Thread Stefan Fritsch
On Wednesday 22 February 2012, Stefan Fritsch wrote: > On Wed, 22 Feb 2012, Rainer Jung wrote: > > Looking at the server status on www.apache.org running 2.3.15 one > > can see, that about 50% of the async connections are in closing > > state. > > > > We created AsyncRequestWorkerFactor to control

Re: AsyncRequestWorkerFactor / Event Sizing / Closing Connections

2012-02-22 Thread Stefan Fritsch
On Wed, 22 Feb 2012, Rainer Jung wrote: Looking at the server status on www.apache.org running 2.3.15 one can see, that about 50% of the async connections are in closing state. We created AsyncRequestWorkerFactor to control the amount of overcommitment in terms of connections relative to idle

Re: AsyncRequestWorkerFactor / Event Sizing / Closing Connections

2012-02-22 Thread Rainer Jung
On 22.02.2012 09:53, Daniel Shahaf wrote: Rainer Jung wrote on Wed, Feb 22, 2012 at 04:53:34 +0100: "C" only occasionally, not with such a big percentage. E.g. on the EU mirror running 2.2 and having less traffic there is hardly ever a "C" to notice. Is that an expected 2.4/event difference, or

Re: AsyncRequestWorkerFactor / Event Sizing / Closing Connections

2012-02-22 Thread Daniel Shahaf
Rainer Jung wrote on Wed, Feb 22, 2012 at 04:53:34 +0100: > "C" only occasionally, not with such a big percentage. E.g. on the > EU mirror running 2.2 and having less traffic there is hardly ever a > "C" to notice. Is that an expected 2.4/event difference, or is there > something strange with the u

AsyncRequestWorkerFactor / Event Sizing / Closing Connections

2012-02-21 Thread Rainer Jung
Looking at the server status on www.apache.org running 2.3.15 one can see, that about 50% of the async connections are in closing state. We created AsyncRequestWorkerFactor to control the amount of overcommitment in terms of connections relative to idle workers we allow for each process. The f