Hi Scott,
that's really very interesting!
> Be aware that using keepalive holds a connection open for longer
> periods of time; I haven't looked at the code to determine whether
> those connections take up a slot in the 'maxconnections' bucket, but
> I suspect that they do as AOLserver needs to maintain the connection
> information.
I assume default settings of
listenbacklog = 32
maxconnections = 100
maxthreads = 10
Would it be correct to say:
(A)
If keepalive is turned off and it is known or very likely that your threads
are long running and computing expensive tasks, "listenbacklog" may become a
limiting factor when "maxthreads" (default 10) are reached and waste away in
parallel. The 23rd+ visitor/request would be dropped (listenbacklog minus
maxthreads).
"maxconnections" is not really relevant here.
(B)
If keepalive is turned on at least "maxconnections" people are served for a
keepalive period of time. Not every request is served immediately of course
that depends on "maxthreads".
Let's assume 10 threads serve 10 connections each ("maxconnections" reached)
then there is a "buffer" of "listenbacklog" for new requests.
The 133rd request is dropped.
Scenario (A) and (B) always assume "maxthreads" are reached.
In (A) it would make sense to increase the "listenbacklog".
In (B) it would make sense to increase "maxconnections".
Of course, increasing "maxthreads" would also work, depending on the available
memory resources.
Ha, and the admin of (B) could trick and set "connsperthread" = 1 ... ;-)
Bernd.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
