cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robby Pelssers" <...@agp.nl>
Subject RE: Problem with tuning JVM (high CPU load)
Date Wed, 23 May 2007 08:23:34 GMT
Hi Thomas,

The behaviour we see is that the CPU load gradually increases and at a
certain point never goes down while we don't see much action taking
place when monitoring the apache server-status.  Also we still have
around 6G free memory at the time that the CPU remains at about 94%
load.  Heap Size boundaries are Xms=12G=Xmx.

Cheers,
Robby

-----Oorspronkelijk bericht-----
Van: Thomas Markus [mailto:t.markus@proventis.net] 
Verzonden: woensdag, mei 2007 9:59
Aan: users@cocoon.apache.org
Onderwerp: Re: Problem with tuning JVM (high CPU load)

if your free memory is low, the jvm runs the gc automatically. in case 
your free memory is very low the gc runs very often and consumes a lot 
of cpu. try to log your current memory state in that situation.

Robby Pelssers schrieb:
> Hi Thomas,
>
> Actually, we scheduled the garbage collector as a cron job to run
every
> day at night between 2 and 3 o'clock two times to make sure memory is
> freed up when daily operations start again around 7-8 o'clock.  I
don't
> really see how running the garbage collector can have a negative
affect?
> And even if there is a memory leak, how do you explain the high CPU
> load?
>
> Cheers,
> Robby 
>
> -----Oorspronkelijk bericht-----
> Van: Thomas Markus [mailto:t.markus@proventis.net] 
> Verzonden: woensdag, mei 2007 9:26
> Aan: users@cocoon.apache.org
> Onderwerp: Re: Problem with tuning JVM (high CPU load)
>
> Hi,
>
> looks like a memory leak. maybe the garbage collector runs very often
>
> thomas
>
>
> Robby Pelssers schrieb:
>   
>> Hi all,
>>
>> we have cocoon2.1.10 running on a solaris(OS version5.8).  The server

>> has 16G of memory and 2 processors (sparcv9 processors operating at 
>> 900 MHz). Cocoon is running on tomcat/4.1.24.
>>
>> After a while we see our CPU increasing to about 94% and the system 
>> becomes non-responsive.  Could anybody point to what we look for?  We

>> can't trace the problem back from the tomcat loggings.
>>
>> Cheers,
>> Robby Pelssers
>>
>>     
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message