httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <>
Subject Re: [PATCH] Change algorithm for spare server maintanence
Date Tue, 20 Apr 1999 22:11:35 GMT

On Tue, 20 Apr 1999, Manoj Kasichainula wrote:

> On Tue, Apr 20, 1999 at 09:26:37AM -0700, Dean Gaudet wrote:
> > To be honest I'd rather see a fixed number of children with a variable
> > number of threads each.  Each of them maintaining their own (portion of
> > the) scoreboard.
> I'm not so sure. When we've hit MaxThreadsPerChild in every process,
> we should be able to start more processes. At the same time, if we

No we shouldn't.  If I say "do not run more than N concurrent children,
and no more than M conncurent threads in any one child" then the server
better stop there.  Otherwise what's the sense having those directives? 

Also, I want to be able to say "run one process and scale the number of
threads".  I also want to be able to say "run four processes because I
have 4 CPUs in this SMP box, and I'm using user-level threads". 

Other than replacing a child which dies, I don't see why we need to spawn
more children ... 


> have a lot of processes running with a few threads, it would be nice
> to collapse some of these threads together into fewer processes,
> though it's not that big a deal.
> To implement something like this, I think you need to have pipes from
> the parent to each child. This means that you limit your number of
> child processes to the maximum number of file descriptors, but this
> isn't too big of a deal since each of our children can use the
> maximum number of threads.
> Manoj

View raw message