> 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). Anyway, I'm almost sure that GnuGK will crash with 10 Setup/sec. This way you'll have 20E1 in ONE minite. We may consider it the top level for full proxy installs. To keep the number of sim. calls in this level we need 10 ReleaseComplete/sec. So, ACD will be < 60 sec. which may occur only if you are the last priority (e.g. 15th) gateway for a given destination. > Another thing is that processing large socket select lists is not efficient > - it is probably better to split them among multiple threads. Won't context switching be more expensive then that socket list processing? Andrey. ------------------------------------------------------- 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/
