7 Aug
2010
7 Aug
'10
5:12 p.m.
Hi Hugo,
On Sat, Aug 07, 2010 at 05:40:02PM +0100, Hugo Mills wrote:
On Sat, Aug 07, 2010 at 03:45:27PM +0000, Andy Smith
wrote:
Agreed.
However in this case there appears to be a memory leak somewhere
inside PHP or Apache and judging from what popey has experienced,
all the apache children grow really huge (several hundred MiB each).
So I don't think that limiting the number of them is going to help
in this instance.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
"Whoever is responsible for this stunning design failure deserves continuous
cockpunches." -- jwz
You could also set a ulimit on the amount of
virtual memory that
apache can have, so it would just kill apache.
Or simply limit the number of apache processes in the apache config
file. I've had a couple of machines that have done this in the past,
and cutting down the number of copies of Apache that can be running at
any one time has solved it. The limits that Debian, for example, ship
with are massively over-sized for a small VPS.