portals-jetspeed-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luta, Raphael (VUN)" <Raphael.L...@groupvu.Com>
Subject RE: Jetspeed Performance tips
Date Thu, 20 Mar 2003 09:40:36 GMT

Is it a temporary peak or do you see a sustained increase in the 
usage after the peak ?

Is your portlet set as cacheable in the portal ? If so what is your
cache expire time ?

Do you have the feaddaemon/diskdaemon running ? If so, it will negatively
impact the performance while running.

Finally, what is the memory available to your webapp server ? Peak
in response times may be correlated to garbage collection (profile
memory usage vs response time to make sure). The overall memory
overhead of processing a Jetspeed page is *much* higher than that of 
a simple JSP.
If you have too much memory available to your webapp server, Jetspeed
will create objects until your reach the high mark memory limit, and 
then trigger the GC which may take significant processing time to 
free a large amount of objects...
Try experimenting with the different GC settings on your platform 
for optimal results (or use multiple server instances with lower
memory limits for each).

Raphaël Luta - raphael@apache.org
Jakarta Jetspeed - Enterprise Portal in Java

> -----Message d'origine-----
> De : Shan Gopalakrishnan [mailto:sgopalak@cisco.com]
> Envoyé : jeudi 20 mars 2003 02:03
> À : Jetspeed Users List
> Objet : Jetspeed Performance tips
> Hello all,
> Thanks for the great posting on Jetspeed mailing list.  We 
> are evaluating 
> Jetspeed for use in a project within Cisco.  I hope you can 
> shed some light 
> on some of the problems we are facing.
> In a very simple test of one portlet that has fixed content 
> (no business 
> logic, no database access, etc.), we have observed some 
> weired behavior and 
> are suspecting Jetspeed is the cause.  We use LoadRunner to run 100 
> concurrent users that pull the same page that has the one 
> portlet of fixed 
> content.  It runs smoothly for about 25 minutes (it takes 
> about 16 minutes 
> to ramp up the 100 users) and then the response time starts 
> to climb quite 
> sharply form < 1s to 8s and then to > 20s or higher while CPU 
> goes from 75% 
> to 45%.  We put the same logic in the plain JSP and ran it 
> with the same 
> load and response time was always flat under 1s. We put in 
> the recommended 
> Jetspeed settings.
> 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.
> Thanks!
> - Shan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org

Vivendi Universal - HTTP://www.vivendiUniversal.com: 
The information transmitted is intended only for the person or entity
to which it is addressed and may contain confidential and/or privileged
material of Vivendi Universal which is for the exclusive use of the
individual designated above as the recipient. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon, 
this information by persons or entities other than the intended recipient 
is prohibited. If you received this in error, please contact immediately 
the sender by returning e-mail and delete the material from any computer. 
If you are not the specified recipient, you are hereby notified that all 
disclosure, reproduction, distribution or action taken on the basis of this 
message is prohibited.

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

View raw message