Appreciated previous posters' replies... very helpful!
Now in the progress of spiffying up the web services into
something beyond just some cgi's, counter, and users' HTML pages.
Got SSI's and Apache configured to my satisfaction... first 30
seconds, it zooooooomed. :)
All of a sudden, the web server (486DX4/120? running Linux 1.3.3)
and Apache 0.8.14 is *really* slagging. Looking at ps Saxugw over two days
seems to indicate two things. (btw, this is a 32 meg machine - 32 of physical
RAM in addition to ~40 megs of swap with a single drive.. a barracuda, I
1) the parent httpd process has an large amount of CPU time - i.e.
1:00 worth of CPU every 60 seconds. Is this normal?
2) What I'm more interested right now is why cgi's are eating
up so much... i.e. typically they (most are counters) are eating up 99% of
the CPU. If it isn't 99%, it's between 20-25% with the parent httpd eating
Is this normal? I have no real frame of reference to compare. If
not, would this indicate a bug, or more likely, a mis-tuned server?
Right now, the site is getting around 160,000 hits/day (say...
approx 6000 hits/hr). MinSpareServers is 5, MaxSpareServers is 10,
StartServers is 5, MaxClients is 100, and MaxRequeustsPerChild is 30.
Also, I'm now seeing about a billion lines in the error log
for: send timed out for [site], script timed out, and receive timed
out. What does this mean/indicate?
Any suggestions on how to tune more effectively under Linux?
I noticed some docs on this on www.apache.org, but seemed to be a bit
on the sparse side - was hoping anybody with experience with Apache/Linux
(or even just Apache in general) could offer more tips.
Any help or pointers would *greatly* be appreciated, suffice
to say! ;-) As I'm really stumped, I'll summarize any posts/mail for