Robert Blayzor wrote: > On 4/2/04 10:53 AM, "Jesse Guardiani" <[EMAIL PROTECTED]> wrote: > >> Howdy list, >> >> >> # uname -a >> FreeBSD chortos.wingnet.net 4.8-RELEASE FreeBSD 4.8-RELEASE #0: Fri Apr >> 11 >> 12:59:08 EDT 2003 >> [EMAIL PROTECTED]:/usr/src/sys/compile/CHORTOS i386 >> >> MaxThreads 5 >> ThreadTimeout 500 > > Maybe it's just me, but doesn't five threads seem just a little low for a > mail server?
Why would you want to run more than five threads concurrently on a single processor box? Queue the remaining connections (and make sure your queue is large enough) and you'll run more efficiently by avoiding thread context switching and such. 5 threads are quite capable of bringing my CPU to 0% idle. My mailserver doesn't reject any mail with only 5 threads. The high MaxConnectionQueueLength insures (or should insure) that incoming messages wait their turn to be processed. Having a lower thread count insures that my server isn't brought to it's knees by high incoming mail volume. If I had 2 CPUs on a Solaris, Linux, or FreeBSD 5.x box then I would probably run 10 threads. 4 CPUs would merit maybe 20-30 threads, etc... Anyway, that's my understanding of the way threading works. If you run too many threads concurrently then you end up wasting a lot of time switching context. If anyone has a good argument against that logic then please let me know. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
