I am experimenting with this in the last two weeks.
Here is what I found so far and I have not completed my study.
In theory if you run something out of process you isolate it to itself.
So if it crashed it only affects that process and nothing else.
If ND can recover from the crash it only need to restart that process.
In ND 4.1.3 I have never seen a crashed worker or service recovered by itself. (I have
seen this in ND 5.0)
So running it out of process for crash protection does not happen in ND 4.1.3 (As far
as I can see).
Running the CP worker out or process for multi cpu machine does make sense.
If you only have one process for all the cp workers you are only able to use one cpu
chip to process all your cp workers.
Running other service and workers out of process is less efficient and ND performance
under stress test is worst.
For IIS 4.0 I have seen numbers of 25% more overhead if you run your application out
of process.
I suspect something simular is also true for ND 4.1.3.
As of today, my best configuration for one of my biggest project is 4 cp worker out of
process each with 5 clients.
Full preload for 5 clients.
If I do not do a complete full preload it will crash ND if I start out with a lot of
users (more than 50 users) at once.
The preloading is slow and only use one cpu chip (ND is only using one process for
preloading)
"PERRY HUNCHAK" <[EMAIL PROTECTED]> wrote:
>What is the advantage of running ND Command Center Processes separately? =
>When should you enable "Run service as separate process"?
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
