Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:12592
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <20040905211921.39505.qmail@pb1.pair.com>
To: internals@lists.php.net
Date: Sun, 05 Sep 2004 22:21:43 +0100
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
MIME-Version: 1.0
References: <20040905193319.91641.qmail@pb1.pair.com>
In-Reply-To: <20040905193319.91641.qmail@pb1.pair.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Really odd PHP problem
From: russ@last.fm (Russ Garrett)

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