portals-jetspeed-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shan Gopalakrishnan <sgopa...@cisco.com>
Subject Re: Jetspeed Performance tips
Date Fri, 21 Mar 2003 16:58:03 GMT
We observed few more things.  I'm posting this to the best interest to 
mature the framework further than what it is currently today.
Definitely this is not criticism.

We are seeing the Garbage collector (Major GC) getting triggered frequently 
as I think huge set of objects are getting created.
This could be inherited from Turbine implementation.  We are now playing 
with the various options in the Garbage Collector
part of the JDK 1.4.1, which is running the GC parallel, setting high heap 
size,  giving some % for young generation Vs old generation etc.
Most likely to my knowledge the minor GC looks only the younger generation 
area as we didn't see any benefits in increase the
% of younger generation.  Apparently the spike still remains and gives poor 
response time just that the symptom happens way early
or later during the tests depending on the heap size and GC configuration.

- Shan
At 12:43 PM 3/21/2003 +0100, Santiago Gala wrote:
>Santiago Gala wrote:
>>Shan Gopalakrishnan wrote:
>>>Has any one done similar  tests, did you observe something like that?
>>>Do you have any suggestions where to look further?  This is on Solaris 8 
>>>with JDK 1.4.1_01, Tomcat 4.1.18 and Jetspeed 1.4b3.
>may well be related. A very scary bug, BTW, which can explain why I'm 
>seeing ant or maven builds hung forever and claim all memory in my 
>machine. Ans also server VM crashes with OutOfMemory after tomcat context 
>Santiago Gala
>High Sierra Technology, S.L. (http://hisitech.com)
>To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org

To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org

View raw message