Re: JPL config file

[Randy Terbush <ra...@zyzzyva.com>]

> Yup, his biggest problem is memory.  He may want to bump down MaxClients a
> bit; he could get better performance if the machine isn't swapping to
> hell.  
> 
> Compiling with the fewest possible modules could help the memory a bit.
> 
> Unfortunately, if I were him with such resources (64 meg is nothing,
> especially on a RISC box) my best solution would be Zeus.  Apache performs
> well, but one process per request just can't compare to one process for
> everything if you don't have the memory.
> 
> I note he has a ScoreBoardFile directive... verify that it is compiled to
> MMAP it (in which case ScoreBoardFile does nothing), as is the default for
> Solaris, if that is what is running. 

Yes, I assumed it was an artifact of the distributed config files. 
I'll verify that it is ignored on systems supporting MMAP.

I'll pass along the suggestions and see if I can get an idea of 
what modules are being used.


> On Sun, 6 Jul 1997, Randy Terbush wrote:
> 
> > 
> > I've exchanged a few emails with one of the responsible people at 
> > JPL. He indicates the following:
> > 
> > > Our web site is split across two servers, www-a.jpl.nasa.gov and
> > > www-b.jpl.nasa.gov.  These are both mirrors of a third machine,
> > > www-onlab.jpl.nasa.gov.  The www-onlab machine is restricted to
> > > JPL internal access only.  Www-a and www-b share the load of
> > > accesses to www.jpl.nasa.gov via round-robin DNS.  All of our
> > > machines are Sun Ultra 1's (170 MHz) with 64 MB of memory and
> > > something like 11 gigs of disk each.  We're running Apache httpd
> > > 1.2b7.
> > 
> > The first problem looks like a shortage of memory, but he goes on 
> > to say that the CPU is 90% idle. I have asked about listen queue 
> > size but don't have that data yet. Being Solaris, they might 
> > benefit from 1.2.1.
> > 
> > Relevant config is below. Basically a stock httpd.conf file with 
> > comments removed (by me). They could probably safely raise the 
> > MaxRequestPerChild value, but based on the CPU load, I don't think 
> > that it is forking a lot.
> > 
> > I've not made any recommendation other than memory at this point. 
> > If someone here would like to contact them directly, send me 
> > private email.
> > 
> > ------- Forwarded Message
> > 
> > ServerType standalone
> > 
> > Port 80
> > 
> > HostnameLookups off
> > 
> > ScoreBoardFile logs/apache_runtime_status
> > 
> > ServerName www.jpl.nasa.gov
> > 
> > Timeout 1200
> > 
> > MinSpareServers 100
> > MaxSpareServers 200
> > StartServers 100 
> > MaxClients 512
> > MaxRequestsPerChild 50
> > 
> > ------- End of Forwarded Message
> > 
> > 
> >