Bill Stoddard wrote:
> A few other benefits to Pauls design:
> 1. Eliminates the requirement for compiled in HARD_SERVER_LIMIT or HARD_THREAD_LIMIT.
> 2. You don't need to allocate child score if you don't care about mod_status (but it
>can
> be added during a restart)
> 3. If you choose to not enable mod_status, you will likely see a nice performance
>boost on
> multi CPU machines because we are not invalidating a CPUs cache each time we touch a
> worker score entry (which is on every request).
> 4. Does not require any changes to the MPM. Each MPM can start threads according to
>its'
> ThreadsPerChild setting w/o needing to pay attention to the scoreboard (I believe
>your
> design required child processes to wait for worker score slots to become available
>before
> it can start threads. This is imposing too much unnecessary work on the MPM.).
5. It fixes the problem with the threaded mpm where no work can be done while workers
are
quiescing due to MRPC, leaving processes with a small number of workers finishing their
last responses and no workers available to process new requests.
--
Paul J. Reder
-----------------------------------------------------------
"The strength of the Constitution lies entirely in the determination of each
citizen to defend it. Only if every single citizen feels duty bound to do
his share in this defense are the constitutional rights secure."
-- Albert Einstein
