Jim this writeup is great.
What you write coincides with my own analyses two months ago when upgrading
nsunix to AOLserver 3.3.
If I understand your question then my guess as to the advantage of
accepting connections even when there are no threads available is thus:
1. We know it's the typical case that you can have 100 connections and only
ten threads, so by default you have to be able to accept more connections
than threads.
2. Connections can block for i/o (waiting for the 300 baud dial up user using
a 20 year old trs-100, so you would want a thread to be able to handle
more than one connection
3. If you aren't being slashdotted and the high traffic is temporary, than
accepting the connection and holding onto it until a thread becomes
available probably keeps the browser from timing out more often than
in the case where the connection isn't accepted until a thread becomes
available.
>I don't quite understand the value of accepting connections even
>though there is no thread available to service the request (this
>occurs if maxconnections > maxthreads). From my point of view as a
>webmaster, I will probably set maxconnections and maxthreads equal.
>This way, if a browser hits our site and no thread is available, the
>user will see "contacting blah.com" during the delay and assume there
>is some network problem. If I set maxconnections > maxthreads and
>maxthreads is too low, users will see "blah.com contacted, waiting for
>reply" and it'll look like our site is slow. Okay - a bit deceitful.
Jerry
========================================================
Jerry Asher [EMAIL PROTECTED]
1678 Shattuck Avenue Suite 161 Tel: (510) 549-2980
Berkeley, CA 94709 Fax: (877) 311-8688
