Costin Manolache wrote:
Further more I don't see how can you avoid keep-alive connection
problems without using a thread-per-connection model.
The point is that with 100 keep-alive connections you will still
have 100 busy threads.
Why ? 100 keep alive connections doesn't mean 100 active requests,
in real servers there are many 'keep alive' connections that are just
waiting for the next request.
Where are they waiting if in blocking mode?
IIRC each is inside a separate thread.
In all servers I know, concurrency was higher than the configured number
of workers - at peak time, at least, where performance matters.
Sure, but this is for accepting new connections, right?
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
