Thanks for all the prompt responses, most appreciated.
Firstly I forgot to add in a fairly crucial subdomain to my hits estimate (I'm half asleep today). It's closer to 2 million dynamic hits per day, all added in, which make my numbers a little more reasonable...
I doubt the spiralling-crash theory because sometimes the server will run fine for hours, using less than 1GB of the 2GB of RAM, and then suddenly die. It tends to die as frequently during off-peak times as it does during peak times. Plus, we're running at a modest MaxClients setting of 100, which with dual 2.4 Xeons and 2GB of RAM should be more than reasonable.
I tend to agree that it may be a case of the crash causing the opcode cache to be corrupted, and causing the rest of the apache processes to hang.
APC doesn't seem to work at all as a DSO, I'll try it statically later.
We can't run without an opcode cache, I just tried it and it completely maxes out the CPU and causes the load to go over 100. We are two fairly heavy Smarty-based sites.
Cheers,
Russ
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
