On Wed, 28 Feb 2001, Ian Holsman wrote:
> Using a un-modifed apache 1.3 v19 code I get
> ~330 pages/second with the load average at about 6, with a average
> response time of 116ms (stddev 341ms)
>
> using apache 2 (cvs from this morning) threaded MPM :
> ~181 pages/second with a load average at about 5 with a average
> response time of 245ms (stddev 345ms)
>
> Using apache 2 ( a12 from web site) prefork MPM:
> ~330 pages/second with a load average of about 4 with a average
> response time of 119.31ms (stdev 346ms)
OK, so prefork is managing about the same performance as 1.3.19 (but with
a much lower loadavg) - definitely something wrong with threaded, though!
> what I found with the threads per child MPM was that I was running out
> of open files, so i had to bump up the number of processes
> instead of the number of threads to stop the apache failing.
Ah... I found this problem with a home-made state machine WWW server under
heavy load on Solaris (Japanese/Chinese gateway for non-i18n browsers -
rendered each individual foreign character as a small GIF, so each page
would cause thousands of requests): Solaris often has VERY low
per-process FD limits, which need increasing for server use.
What is it set to? (ulimit -a)
> I guess the real queston I have is about the settings of the threaded
> MPM, I have access to quantify and gprof , and can generate more
> sophisticated
> tests.
James.
