httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua Slive" <jos...@slive.ca>
Subject [PATCH] update to default worker MPM config to match MaxClients fix
Date Thu, 20 Sep 2001 19:54:49 GMT


> -----Original Message-----
> From: Ryan Bloom [mailto:rbb@covalent.net]

> > I think we should also rename MaxClients to MaxWorkers.
>
> I dislike this.  MaxClients still makes sense IMHO.  It is the
> maximum number
> of clients allowed at one time.  MaxWorkers is the maximum number
> of things
> (threads or processes) running at one time.  MaxClients just
> seems easier to
> explain to me.

I understand what you mean, but I disagree.  If you look at my example

> StartWorkers              50
> MaxWorkers               150
> MinSpareWorkers           10
> MaxSpareWorkers           50
> WorkersPerProcess         25
> MaxRequestsPerProcess      0

the beauty is that everything is in the same units and is referenced the
same way.  If you change MaxWorkers to MaxClients, the first question that a
new user would ask is "how do clients differ from workers?".  The answer is
they don't, except in an obscure theoretical way.

I support StartWorkers rather than StartProcesses for the same reason.  I
agree with you that it means lots of stuff going on behind the curtains.
But I think it is worth it to have clear configuration directives.  The docs
(and perhaps the config file) should simply say "MaxWorkers and StartWorkers
should be multiples of WorkersPerProcess."

Joshua.


Mime
View raw message