Hello,
before I asked about why a dec alphastation 255 4/233 with 64 megs of ram
would be dead slow at 42 virtual hosts with 21 processes each. At almost
a total of 900 processes in the process pool I guess its not too hard to
figure out that it was simply swapping itself to death trying to
accomodate this. Anyway, I've put in the apache server (1.0.5) as a drop
in replacement for netscape commerce server and it works great -- with
one exception! It is handling about 50 virtual hosts with no problem and
load averages are back to under 1.00. I've set the apache server up to
use a single parent process to manage requests for all virtual hosts.
This way I don't have to preallocate processes unless there is an active
request for that virtualhost.
This is my question out of the summary: it appears as though apache can
not create any more than 32 processes to handle incoming requests. This
is hardly sufficient and it ends up to the point where a port is
bind()'ed and listed()'ed to but no accept call is being made because no
free proecsses are available to fullfill the request. Any reason for
this albeit strange behavior? I've upped maxuser to 256 and maxuprc to
256 in the kernel and double checked this with dbx. I figure this should
maybe be posted in www-managers or apacghe bugs but I thought it may be
an os issue.
- Thanks in advance
Brad Block
Received on Thu May 23 1996 - 01:09:23 NZST