>
> > -----Original Message-----
> > From: Aaron Bannert [mailto:[EMAIL PROTECTED]]
>
> > <IfModule worker.c>
> > -StartServers 3
> > -MaxClients 8
> > -MinSpareThreads 5
> > +StartServers 2
> > +MaxClients 150
> > +MinSpareThreads 25
> > MaxSpareThreads 75
> > ThreadsPerChild 25
> > MaxRequestsPerChild 0
>
> I think this is going in the right direction. Two comments:
>
> 1. MinSpareThreads is way too high. There is no reason to have 25 idle
> threads hanging around at all times. The original figure of 5 seems fine to
> me.
>
> 2. Naming:
> I think we should define Server="thing capable of serving requests" and
> completely get rid of "Child" which is ambiguous. Then we can change
> MinSpareThreads -> MinSpareServers
> MaxSpareThreads -> MaxSpareServers
> StartServers -> StartProcesses
> ThreadsPerChild -> ThreadsPerProcess
> MaxRequestsPerChild -> MaxRequestsPerServer
This last one is inconsistent with your other changes. In the threaded MPM, a
'Server' by
your defn is a thread. MaxRequestsPerChild is used to limit the number of requests a
'process' serves before going away.
In past discussions, we have almost settled on the notion of a "worker" as being the
thing
capable of serving a request.
MinSpareWorkers
MaxSpareWorkers
StartWorkers - ??? What do we want the option to do? Startup this number of worker
threads
or startup this number of child processes?
WorkersPerProcess
MaxRequestsPerChild (or MaxRequestsPerProcess)
Okay, changing topics only slightly... how about we replace
MinSpare[Threads|Servers|Workers] and MaxSpare[Threads|Servers|workers] with a single
directive, Spare[Threads|Servers|Workers]?
Bill
Bill
