Bug#219378: Runaway number of children
Hi Dave,
I have been doing some load tests on my machine but i cannot
reproduce this problem. To "stress" apache i used the following command in
all my tests:
ab -n 100000 -c 100 http://localhost/
The amount of processes were never exceeding the values specified in the
config for:
MinSpareServers
MaxSpareServers
StartServers
MaxClients
MaxRequestsPerChild
I performed the test using both the default config and a config with
higher values in the previous directives, apache 1.3.29 and 1.3.28.
The only thing i noticed is that apache 1.3.28 seems slower in killing
child than 1.3.29 but this might be highly related to my machine so i
can't really say that there is a difference in here. (it's a very slow
laptop and it has not been rebooted between tests, upgrade/downgrade of
packages and so on).
Can you reproduce this problem on another machine or on the same machine
with the default config?? In the latter case do you have any module
enabled in your config that might cause the problem that are not loaded in
the default config??
Thanks
Fabio
On Wed, 5 Nov 2003, Dave O wrote:
> Package: apache
> Version: 1.3.29-1
>
> After upgrading from 1.3.28-1 to 1.3.29-1 the number of apache children
> under normal use increased dramatically. It appeared as though apache
> would not reuse processes and continued to spawn new ones. After watching
> it climb to ~60 I downgraded back to 1.3.28-1 and it is now running
> normally with ~20 children under the same load
>
>
>
--
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues
http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp00004.html
Reply to: