At 01:29 AM 8/5/01 -0500, John Buwa wrote:
>91 processes: 89 sleeping, 2 running, 0 zombie, 0 stopped
>CPU states: 0.0% user, 0.7% system, 0.0% nice, 99.2% idle
>Mem: 257408K av, 228384K used, 29024K free, 13744K shrd, 5380K buff
>Swap: 265528K av, 184780K used, 80748K free 8908K
>cached
> PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM CTIME COMMAND
>25788 nobody 0 0 126M 125M 1076 S 0.0 49.8 0:13 httpd
><----modperl server
>25787 nobody 0 0 196M 32M 1356 S 0.0 12.9 0:19 httpd
><-----modperl server
>25799 nobody 0 0 32592 30M 8 S 0.0 12.2 0:10 httpd<---Non
>modperl server
Not having read anything before this, but it seems that your machine is
going into swap because there is not enough RAM available. That kills your
performance always. Could you run your test on a different machine or
temporarily switch off the regular server?
Trying to run close to 200 Mbyte modperl Apaches on a 256 Mbyte machine is
not going to work. Have you looked at MaxRequestsPerChild?
But even the non-modperl servers at 30 Mbyte size seems ridiculously large:
are you sure you need all the modules that you compiled into Apache?
Elizabeth Mattijsen
