On Wed, 2004-08-18 at 09:21, Jim Wilcoxson wrote: > ... > > > AOLserver is ideally suited to the majority of server tasks. About the > > > only shortcoming which comes to mind is that conn threads are required > > > to do blocking writes. But fixing that would be of benefit to the HTTP > > > processing side too. > > > > So, we want reader threads and separate writer threads now, too? > > Exactly how many free-range threads do we want roaming the server > > prairie, here? > > You don't need reader threads and writer threads. If input and output > both use event-driven, non-blocking I/O, you can use one thread to do > both, or one thread per CPU, like TUX.
You can't do non blocking I/O on a file descriptor backed by disk. Not portably at least. Calls like stat(2) to get the last mod time may also block. That's why I suggested a pool of writer threads. TUX actually does something very similar to handle potentially blocking disk I/O. One of the biggest resource hogs is not the conn threads themselves but the Tcl interps they drag round with them. If you're interested in cutting down on resource usage, you might want to take a look at this RFE: http://sourceforge.net/tracker/index.php?func=detail&aid=1012103&group_id=3152&atid=353152 -- 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.
