[omniORB] Scalability problems; 300+ clients

[Slawomir Lisznianski]

Ironically we are seeing problems earlier when we use
threadPerConnectionPolicy=0 ;-) When we set threadPerConnectionPolicy=1
we are able to serve slightly more clients (~600) before exceptions
start occuring. The whole time memory footprint of the server is below
1GB with over 6GB free on the box.

Next, we are going to try running server on a 2.6 kernel and see if it
makes any difference.


On Wed, 05 Jul 2006 20:23:14 +0200, "Peter Klotz" <peter.klotz at aon.at>
said:
> We encountered similar problems under Red Hat Enterprise Linux 3 and I 
> tracked it down to the stack size of the server threads. Each thread 
> seems to be created with a stack size of 10MB. The total memory one 
> process is allowed to use is 3GB (at least on i386). This limits the 
> number of threads to approximately 300.
> 
> We disabled threadPerConnectionPolicy (which is 1 by default) and use a 
> thread pool with much less than 300 threads instead.
--
Slawomir Lisznianski
Paramay Group, Inc.
"Programs for Research Machinery"