The problem for Windows is that fd_set structure takes 4 bytes for each handle (while on linux it is one bit/handle), so large fdsets (like 1024) are inefficient under Windows. For Linux, it is enough to do a simple shift and bitmask operation to check the handle. On Windows you need to iterate the whole fdset and comapare each handle value. But I did not measure the overall performance, so it may appear it's not so bad:). Another thing is that with CallSignalHandlerNumber=2 and Setup authentication/accounting modules enabled, the throughput of processed calls is not as good as it could be with greater CallSignalHandlerNumber. Everything is a matter of finding a good balance over number of threads (and context switches) and overall system performance. ----- Original Message ----- From: "Boris V. Kardakov" <B.Kardakov@xxxxxxxxxxxxxx> Sent: Friday, April 02, 2004 3:54 AM > We are using win2k as, all libs compiled with fdset 1024. So every > instance of call signal calling thread call do the select of maximum > 1024 sockets. > From the other hand, we use Dual Pentium Processor(r) platform, so we > can operate more than one thread at one time. ( say, two threads ;) So, > we use CallSignalHandlerNumber=2. > > As a result we have 1024 * 2 signal channels can be served. ------------------------------------------------------- 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 _______________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
