I have a web server farm that right now has about 125 apache processes
running per machine. If I try to use 2.4.3 or even 2.4.3-ac6 it will go to
about 400 (meaning it is slow in clearing connections), the load average
will start to climb until it gets to close to 100 and then stops responding.
It runs ok for about the first 5 minutes of its life and then sinks deeper
and deeper into the mire until it disappears. No processes are shown stuck
in D state.
2.4.4pre3 works, sorta, but is very "pumpy". The load avg will go up to
about 60, then drop, then climb again, then drop. It will vary from very
sluggish performance to snappy and back again to sluggish.
With 2.2 kernels I see something like this:
00:48:00 up 4:51, 1 user, load average: 0.00, 0.02, 0.06
141 processes: 139 sleeping, 2 running, 0 zombie, 0 stopped
CPU states: 2.8% user, 3.2% system, 0.0% nice, 94.1% idle
and that is with about 120 remote users connected to the box via apache.
Is there any information that would be helpful to the kernel developers that
I might be able to provide or is this a known issue that is currently being
worked out?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 15 2001 - 21:00:23 EST