I am not quite sure, but you can give a try. Use require_once() include
like 10 dummy config file, reload the script a couple times, and use lsof
to check if your config files are still open.
Derek
At 03:04 PM 5/9/2001 +1000, Cameron wrote:
>i dont suppose this is a session garbage collectio
ID: 10299
User Update by: [EMAIL PROTECTED]
Status: Critical
Bug Type: Performance problem
Operating system: FreeBSD 4.2 Stable
PHP Version: 4.0.4pl1
Description: CPU and Memory Spike
What I found out is that using a lot of include_once, require_once + session will
trigger the CPU and memory spi
That's my whole point. PHP should be able handle it pretty well. But
Chris Adams said my setup can only support 10 concurrent
connections. That's why I am curious what is wrong here.
I am pretty sure PHP can handle the load, but somehow something trigger the
CPU spike. I just can't find ou
So, I am wondering what will cause the CPU and memory spike? As I said in
my previous mesg, include a lot of files and keep reloading the page will
get the CPU idle time to 0% and then the httpd process hang.
-Original Message-
From: Chris Adams
To: Derek Leung
Sent: 4/15/01 3:21 AM
S
ID: 10299
User Update by: [EMAIL PROTECTED]
Status: Open
Bug Type: Performance problem
Description: CPU and Memory Spike
I found the problem. since the script I use have a lot of include and require
statement. just a script include a bunch of files and keep reloading the page will
kill the se
ID: 10299
User Update by: [EMAIL PROTECTED]
Status: Open
Bug Type: Performance problem
Description: CPU and Memory Spike
This is vmstat show if I keep reloading the script
procs memory pagedisks faults cpu
r b w avm fre flt re pi po fr sr da0
From: [EMAIL PROTECTED]
Operating system: FreeBSD 4.2 Stable
PHP version: 4.0.4pl1
PHP Bug Type: Performance problem
Bug description: CPU and Memory Spike
I am running on FreeBSD 4.2 Stable, Apache 1.3.19 + PHP 4.0.4pl1 + Modssl on a Dual P2
400mhz with 256mb ram. From tim