100 is a bad choice probably, but 1 is not the best one too. If we consider authentication/accounting performed during Setup processing we may find single call signal handler limiting our call throughput. If our average Setup processing time is 100ms, we will not be able to handle more than 10 calls per second (in practice this number is yet smaller). Another thing is that processing large socket select lists is not efficient - it is probably better to split them among multiple threads. ----- Original Message ----- From: "Andrey S Pankov" <casper@kbuapa.kharkov.ua> Sent: Wednesday, November 19, 2003 1:10 PM > > I've seen some production environments where this option has been set to 100 > > or similar value to offer best call throughput. > > Does it help? Do they really have what they expect from setting it to 100? ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
