[OT] Apache on Windows, how many processes?
I know in the *nix world that Apache forks different processes and in Windows it is threaded. I was load testing my Windows Apache Module with 50 clients and it never started up a second process, though the thread count did surpass the 50, it went to 53. I am assuming the other three threads where maintenance threads that are not counted in the thread pool. My question is: Will Apache on Windows start up more then one worker process? If so, what does it take to get that to happen?
Re: [OT] Apache on Windows, how many processes?
On Mon, May 3, 2010 at 11:47 AM, Sam Carleton scarle...@miltonstreet.com wrote: I know in the *nix world that Apache forks different processes and in Windows it is threaded. I was load testing my Windows Apache Module with 50 clients and it never started up a second process, though the thread count did surpass the 50, it went to 53. I am assuming the other three threads where maintenance threads that are not counted in the thread pool. My question is: Will Apache on Windows start up more then one worker process? If so, what does it take to get that to happen? winnt MPM is Limited to 1 child (and 1 parent) -- Eric Covener cove...@gmail.com
Re: [OT] Apache on Windows, how many processes?
On 5/3/2010 11:43 AM, Sam Carleton wrote: Interesting, so what purpose does the parent process preform with MPM winnt? Is it just legacy? No, it's certainly not legacy. It's very easy to have a semistable or unstable httpd process once you add in your efforts to hack custom perl or c modules, etc. The parent ensures that the server stays up, even as a worker process is lost or gracefully quits for MaxRequestsPerChild.
