4 Apr
2011
4 Apr
'11
9:04 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 30/03/11 21:08, Alberto Bertogli wrote:
On Mon, Mar 28, 2011 at 11:10:59AM +0000, Andy Smith
wrote:
That's a nice idea, I'd not heard of that before, I'm going to look into
that.
For some closure, I should say that I've not had a crash in the week
since my original post, having driven the Apache MaxClients down to 10,
which is kind of annoying :-/
It seems incredible that you can't serve more than 10 simultaneous
clients on ~500MB RAM so perhaps it is time to consider an alternative
HTTP server.
Regards,
Adam Sweet
- --
http://blog.adamsweet.org/
If it's always apache2 then it could actually
be apache using all
the memory and going into swap, then being too slow to do anything.
It might be something else though. Or it might not be memory-related
at all.
If it keeps happening maybe you could put Apache in a memory cgroup,
that way if it begins to use too much memory it'll be contained and the
VPS will be fully usable. It will also prevent the OOM killer touch
processes not in that cgroup, and give you a decent environment to debug
the issue.
We've been doing that in our VPS for about a week and it's been working
great for us. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk2ZiZUACgkQRi1ZcmvD37c+oQCfTG+QiHL45DaG0bbtjqVlS41C
DTYAn2B2Ghvplfgh5/C6qyuimtrHBKxN
=iDDq
-----END PGP SIGNATURE-----