[ QUOTE ]
So the question is, where do you have your maximum set? At the moment, we have a typo (in my opinion) on one set of batch servers. The max value was set to 100, the autostart was set to 100. The server has a lot of ram, but that's a little bit over the top. We had around 135 jdenet processes active on the servers. I proposed scaling the number of autostarts back to a more reasonable number. We are waiting for the other CNC to return from vacation before I make that change.
I could see caluculating the maximum load for the server, and autostarting that many, or at least a good chunk, of the call object kernels. At the moment, I would expect to need around 22 call object kernels to support a full load.
Any thoughts on that?
[/ QUOTE ]
The tuning for Call Object kernel has changed since multi-threading was introduced. The old and simple rule of thumb stating x number of processes per x number of users is no longer valid. the new rule of thumbs says to keep the number of Call Object kernels relatively low and allow threads to be spawned, not processes.
Here's what I do:
Calculate based on 2-5 users per thread but set threads per kernel to 20 and increase threads by increasing kernels to meet the number of threads required.
So, answering your question - having 100 CO kernel start sounds like an awful lot. If you assume 5 users per thread and you have 100 kernels with thread pools of 50 then you are autostarting enough threads for 5,000 users on that box. However, knowing how large your implementation is this is not out of range it seems.