Hey Jonathan,
yep. thats the idea.. just that our server network consists of
osx-servers as well... so im not getting around it that easy =/
Was searching around but couldnt pick up any bug-report of this kind
It's no loop, cause i get the confirmation the page is done and the
script is terminated..
And im not starting up new threads myself.. i rely on apache on this so
it feels like i should be in a safe enviroment here.. no work should be
left after the page is done.
the only thing that can distrub is the fact im sharing memory over
threads. But its should only be work for the CPU while im running the
page.. not afterwards, right?
deadlocks should stop me in the middle.. and not progress to the end..
so it sounds distant.
A memory leakage wouldnt torture the cpu like this afaik, just show up
as a climbing number on the memory display so .. feels like im innocent
here..
although it does seems like its just some few big size operations that
triggers it, wich indikates that some rutine can be the cause... thats
about as far as i got in the analyze.. i'll try to isolate it a bit
futher, could be some plugin even though it sounds odd.
~ F
On Dec 6, 2005, at 2:24 PM, Jonathan Vanasco wrote:
i've seen stuff like this on osx a lot -- apache or some other app
will peg for near 100% cpu use for a few moments, then just go idle
no idea why.
there's a VERY good chance this is a mac thing, and your code will be
fine on another server (assuming you're using the mac like me as a dev
box for eventual install on freebsd/linux mchines)
On Dec 6, 2005, at 12:36 AM, Fredrik Lindmark wrote:
PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE
VSIZE
548 httpd 73.3% 0:45.79 62 91 404 26.5M 44.6M 32.4M
110M
547 httpd 0.0% 0:00.00 1 9 231 5.81M 39.1M 708K
59.6M
This is the status aprox. 40 sec after the last page was delivered.
(if i turn off other stuff running here it goes towards 100%
consuming.)
Around 60s after last page was done the process knocks it off and
goes back to idle...
I kinda hope for a bit more traffic than 1 per min.. so any help
would be appreciated.
darwin 10.3.9 / apache 2.2.0 w/ worker / mod_perl 2.0.2 / perl 5.8.1
Had same issue on the apache 2.0.55 version in fact...
~ F
