You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Shan Gopalakrishnan <sg...@cisco.com> on 2003/03/20 02:02:49 UTC

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


Re: Jetspeed Performance tips

Posted by Shan Gopalakrishnan <sg...@cisco.com>.
Santiago


>In all the experiments I have seen (always on 1GB dual PentiumIII 
>machines), Jetspeed degrades sharply at about 50 concurrent requests, and 
>this has not changed in the last year. You could be seeing the same 
>behaviour, but scaled to your CPU, RAM and architecture. I would try to 
>use less concurrent requests (at a sustained rate) to test the limits. Try 
>several hours with 20, then 50, etc. Also, notice that the server hotspot 
>VM needs time to see hotspots and optimize them, and during method 
>compilation it actually slows down the whole system.
Yes, somewhat exact behavior I'm seeing. Below is the hardware config of 
our machine.  We ramped up 1user every 10sec up to 100 users
and the 100 users stayed 30 mts executing bunch of portal actions.  I see 
spikes at 28th minute with just a Hello World portlet. I'm also
investigating JDK1.4.x and Borland 5.x to see any cause. will post you with 
more information. thanks a lot


System Configuration:  Sun Microsystems  sun4u Sun Fire 280R (2 X 
UltraSPARC-III+)
System clock frequency: 150 MHz
Memory size: 4096 Megabytes

========================= CPUs ===============================================

           Run    E$    CPU     CPU
Brd  CPU  MHz    MB   Impl.    Mask
---  ---  ----  ----  -------  ----
  A    0    900   8.0  US-III+  2.2
  B    1    900   8.0  US-III+  2.2

========================= Memory Configuration ===============================

            Logical  Logical  Logical
       MC   Bank     Bank     Bank         DIMM    Interleave  Interleaved
  Brd  ID   num      size     Status       Size    Factor      with
----  ---  ----     ------   -----------  ------  ----------  -----------
  CA    0     0      2048MB   no_status    1024MB     2-way        0
  CA    0     2      2048MB   no_status    1024MB     2-way        0




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


Re: Jetspeed Performance tips

Posted by Santiago Gala <sg...@hisitech.com>.
Shan Gopalakrishnan wrote:

(...)
>> About Spring 2001 some profiling and tuning was done, by the IBM team, 
>> David, Raphael and myself. I don't know of other such effort since 
>> then. This led to rundata and some other objects pooling in turbine, 
>> and some changes of String concatenation to StringBuffer.append(). We 
>> also discovered a lot of duplicated initializations and similar stuff. 
>> It is always funny to see how big bugs can hide in code.
> 
> --------->> This really makes us think twice whether we can use it for 
> production. I would appreciate if profiling/tuning can be treated much 
> frequently to develop a healthy framework.  Hopefully some of our 
> results /analysis will help the development team.
> 

We have a Jetspeed derivative running on a dual PentiumIII with 1GB of 
RAM and external DB. It is taking a sustained load of 600 sessions a 
day, with about 6000 portal page views a day.

We have yet to see a problem with it. You see normally loads around 2-3% 
on this machine. I think it can handle up to ten times the current load 
with no problem, and then we will start putting more "iron" to the task. 
We routinely restart tomcat to make minor changes (let's say every 7-15 
days). But otherwise it runs unnoticed

You should not plan for more than about 50-60% sustained cpu load. I 
would put a dual PentiumIII box for each 10 expected concurrent requests 
in the system. (as a rule of thumb). This will be more fault tolerant, 
as you can add/remove machines by just taking them out of the scheduler 
and waiting till sessions expire.


If a user asks for a page every minute, and service takes a second, 10 
concurrent requests mean 600 simultaneous users.


In all the experiments I have seen (always on 1GB dual PentiumIII 
machines), Jetspeed degrades sharply at about 50 concurrent requests, 
and this has not changed in the last year. You could be seeing the same 
behaviour, but scaled to your CPU, RAM and architecture. I would try to 
use less concurrent requests (at a sustained rate) to test the limits. 
Try several hours with 20, then 50, etc. Also, notice that the server 
hotspot VM needs time to see hotspots and optimize them, and during 
method compilation it actually slows down the whole system.


>>
>> If the problem is that some "bunches" of objects get into "old" space 
>> because they are pointed by persistent objects, then a juditious 
>> ammount of "= null" on recycling can help a lot. I've just checked 
>> DefaultJetspeedRunData and it is disposed properly (unless something 
>> is broken down in Turbine and it is not really disposed).
> 
> ----->>>Good point. I used to wonder how Jetspeed (team) will handle for 
> the inherent problems of Turbine ??
> 

We can ask them to patch (in fact, David is committer in turbine-2) We 
have done it in the past, and will do it again if needed.

During some period Raphael had to patch turbine and we used a patched 
version, until we got the needed changes inside turbine.

> Thanks a lot for all your information.
> 
> - Shan
> 


-- 
Santiago Gala
High Sierra Technology, S.L. (http://hisitech.com)
http://memojo.com?page=SantiagoGalaBlog



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


Re: Jetspeed Performance tips

Posted by Shan Gopalakrishnan <sg...@cisco.com>.
Santiago,

Thanks a lot for all your information.  my comments in line

At 07:38 PM 3/21/2003 +0100, Santiago Gala wrote:
>Shan Gopalakrishnan wrote:
>>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.
>
>Feel free to criticize. It is the only way we have to improve Jetspeed.

--------->>Thanks and i will exchange whatever we learn part of our 
analysis and testing


>>We are seeing the Garbage collector (Major GC) getting triggered 
>>frequently as I think huge set of objects are getting created.
>
>Some profiling could be handy. AFAIK:

--------->> We will be doing this with OptimizeIt. will share that with you.


>Wrappers for security are not recycled (they *must* be inmutable)
>PortletSets are created new for every request, due to threading issues.
>--> Both kinds of objects should be claimed from "young" space, unless we 
>are missing some "nullification" in permanent objects.

--------->>As we see the minor GC is not clearing up much objects, we still 
think there is some missing nullification in the permanent objects
            as we also notice the memory keeps growing.


>Every 30m you will have tomcat sessions expiring. If your testing does not 
>keeps the sessions, you will be filling a lot of memory with fake sessions 
>which will never be reused. I imagine you are using a testing framework 
>that keeps sessions for a number of hits per "user".

--------->>we ensured this . the session id is passed through a cookie and 
this is reused between requests from the same user

>A lot of other objects could come from either Velocity ASTs, Torque peers 
>or other places. Even from your portlets ;-)
>
>About Spring 2001 some profiling and tuning was done, by the IBM team, 
>David, Raphael and myself. I don't know of other such effort since then. 
>This led to rundata and some other objects pooling in turbine, and some 
>changes of String concatenation to StringBuffer.append(). We also 
>discovered a lot of duplicated initializations and similar stuff. It is 
>always funny to see how big bugs can hide in code.
--------->> This really makes us think twice whether we can use it for 
production. I would appreciate if profiling/tuning can be treated much 
frequently to develop a healthy framework.  Hopefully some of our results 
/analysis will help the development team.


>But the behaviour you are seeing looks more like the bug I pointed below 
>or a bug in the hotspot compiler. Could you switch temporarily to jdk 
>1.3.1_07 or 1.4.0_XX and see if the same happens? (According to reports in 
>cocoon-dev, 1.4.0 does not have the StringBuffer bug)

--------->>  I tried changing this. unfortunately changing it to 1.4.0.xx 
resulted in a slower performance which is substantial and noticeable. i 
couldn't believe. looked it and tried more than once to ensure it happens. 
and yes it happens.


>>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.
>
>If the problem is that some "bunches" of objects get into "old" space 
>because they are pointed by persistent objects, then a juditious ammount 
>of "= null" on recycling can help a lot. I've just checked 
>DefaultJetspeedRunData and it is disposed properly (unless something is 
>broken down in Turbine and it is not really disposed).
----->>>Good point. I used to wonder how Jetspeed (team) will handle for 
the inherent problems of Turbine ??

Thanks a lot for all your information.

- Shan

RE: Disabling Torque

Posted by Shan Gopalakrishnan <sg...@cisco.com>.
Got it. Thanks David.

-----Original Message-----
From: David Sean Taylor [mailto:david@bluesunrise.com] 
Sent: Tuesday, April 22, 2003 3:31 AM
To: Jetspeed Users List
Subject: Re: Disabling Torque



On Monday, April 21, 2003, at 06:36  PM, Shan Gopalakrishnan wrote:

> Can anyone from the development appreciate if you can share some 
> pointers on disabling Torque.? Does it mean we have to change the 
> underlying implementations like 
> UserManagement,RoleManagement,PsmlManagement etc.
>
In the default implementation, Torque is used only by the Security 
services and the Coffees demo portlet
There is nothing stopping you from using JDBC in your portlets. In fact
you can use JDBC, and still get your connections from Torque's 
pool
Or you can completely bypass Torque.

One easy way to disable Torque is to use the no-security implementation 
of the security services.
But then you have no security!
The Jetspeed website describes writing your own Security 
implementation. See the link off the main page called "Security"

--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
+01 707 773-4646




---------------------------------------------------------------------
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


Re: Disabling Torque

Posted by David Sean Taylor <da...@bluesunrise.com>.
On Monday, April 21, 2003, at 06:36  PM, Shan Gopalakrishnan wrote:

> Can anyone from the development appreciate if you can share some
> pointers on disabling Torque.? Does it mean we have to change the
> underlying implementations like
> UserManagement,RoleManagement,PsmlManagement etc.
>
In the default implementation, Torque is used only by the Security 
services and the Coffees demo portlet
There is nothing stopping you from using JDBC in your portlets.
In fact you can use JDBC, and still get your connections from Torque's 
pool
Or you can completely bypass Torque.

One easy way to disable Torque is to use the no-security implementation 
of the security services.
But then you have no security!
The Jetspeed website describes writing your own Security 
implementation. See the link off the main page called "Security"

--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
+01 707 773-4646




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


Disabling Torque

Posted by Shan Gopalakrishnan <sg...@cisco.com>.
Can anyone from the development appreciate if you can share some
pointers on disabling Torque.? Does it mean we have to change the
underlying implementations like
UserManagement,RoleManagement,PsmlManagement etc.

Thanks

- Shan


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


Portal/ Portlet Authorization

Posted by Shan Gopalakrishnan <sg...@cisco.com>.
Hello all

In our application we have a requirement to use our own authorization
because eventually we will use tools like 
SiteMinder.  I saw an interface to plug our own implementation which is
PortalAccessController.
Based on this I have the below question

If I provide an alternate implemenation for RegistryAccessController
example and put that in the 
JetspeedSecurity.properties will it be ok?. I also see the
JetspeedSecurity Class which is a 
commodity static accessor class around the JetspeedSecurityService. The
JetspeedSecurityService
is in turn referencing the underlying JetspeedDBSecurityService.
Appreciate if someone can explain
what is  the flow here between these objects.

Thanks



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


Re: Jetspeed Performance tips

Posted by Shan Gopalakrishnan <sg...@cisco.com>.
Santiago

Another useful information.  We set the heap size to 750meg.  The users 
load tested are 100 users with a think time of 30sec to 60secs
We see the major GC starts when the heap is full and clears  550meg of 
memory with live objects using 200meg. with in a span of another
5 secs , we see the remaining 550meg is again used and the major GC is 
triggered.  the response time suffers during the major GC running period.

Hope this helps

- Shan


At 07:38 PM 3/21/2003 +0100, Santiago Gala wrote:
>Shan Gopalakrishnan wrote:
>>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.
>
>Feel free to criticize. It is the only way we have to improve Jetspeed.
>
>>We are seeing the Garbage collector (Major GC) getting triggered 
>>frequently as I think huge set of objects are getting created.
>
>Some profiling could be handy. AFAIK:
>
>Wrappers for security are not recycled (they *must* be inmutable)
>PortletSets are created new for every request, due to threading issues.
>--> Both kinds of objects should be claimed from "young" space, unless we 
>are missing some "nullification" in permanent objects.
>
>The registries are reloaded every 5 minutes, meaning a whole set of Castor 
>marshalling and new objects going on (and fading) happens. If you don't 
>have registries that change a lot, you could make this interval greater.
>
>Every time DiskCacheDaemon runs, it will call xerces and xalan to 
>transform RSSPortlets.
>
>Every 30m you will have tomcat sessions expiring. If your testing does not 
>keeps the sessions, you will be filling a lot of memory with fake sessions 
>which will never be reused. I imagine you are using a testing framework 
>that keeps sessions for a number of hits per "user".
>
>A lot of other objects could come from either Velocity ASTs, Torque peers 
>or other places. Even from your portlets ;-)
>
>About Spring 2001 some profiling and tuning was done, by the IBM team, 
>David, Raphael and myself. I don't know of other such effort since then. 
>This led to rundata and some other objects pooling in turbine, and some 
>changes of String concatenation to StringBuffer.append(). We also 
>discovered a lot of duplicated initializations and similar stuff. It is 
>always funny to see how big bugs can hide in code.
>
>But the behaviour you are seeing looks more like the bug I pointed below 
>or a bug in the hotspot compiler. Could you switch temporarily to jdk 
>1.3.1_07 or 1.4.0_XX and see if the same happens? (According to reports in 
>cocoon-dev, 1.4.0 does not have the StringBuffer bug)
>
>>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.
>
>If the problem is that some "bunches" of objects get into "old" space 
>because they are pointed by persistent objects, then a juditious ammount 
>of "= null" on recycling can help a lot. I've just checked 
>DefaultJetspeedRunData and it is disposed properly (unless something is 
>broken down in Turbine and it is not really disposed).
>
>>- 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.
>>>
>>>
>>>http://developer.java.sun.com/developer/bugParade/bugs/4724129.html
>>>
>>>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 reloading.
>
>
>--
>Santiago Gala
>High Sierra Technology, S.L. (http://hisitech.com)
>http://memojo.com?page=SantiagoGalaBlog
>
>
>
>---------------------------------------------------------------------
>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


Add context data to default.vm

Posted by Ryan Christianson <ry...@echospace.com>.
I'd like to add a object to the default.vm context. Normally, to add 
data to the context I would create a VelocityAction class, and add it to 
the context there. However I can't figure what action is used to build 
the default.vm screen. Is there a way to do this?

Thanks!

Ryan Christianson


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


Re: Jetspeed Performance tips

Posted by Santiago Gala <sg...@hisitech.com>.
Shan Gopalakrishnan wrote:
> 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.

Feel free to criticize. It is the only way we have to improve Jetspeed.

> 
> We are seeing the Garbage collector (Major GC) getting triggered 
> frequently as I think huge set of objects are getting created.

Some profiling could be handy. AFAIK:

Wrappers for security are not recycled (they *must* be inmutable)
PortletSets are created new for every request, due to threading issues.
--> Both kinds of objects should be claimed from "young" space, unless 
we are missing some "nullification" in permanent objects.

The registries are reloaded every 5 minutes, meaning a whole set of 
Castor marshalling and new objects going on (and fading) happens. If you 
don't have registries that change a lot, you could make this interval 
greater.

Every time DiskCacheDaemon runs, it will call xerces and xalan to 
transform RSSPortlets.

Every 30m you will have tomcat sessions expiring. If your testing does 
not keeps the sessions, you will be filling a lot of memory with fake 
sessions which will never be reused. I imagine you are using a testing 
framework that keeps sessions for a number of hits per "user".

A lot of other objects could come from either Velocity ASTs, Torque 
peers or other places. Even from your portlets ;-)

About Spring 2001 some profiling and tuning was done, by the IBM team, 
David, Raphael and myself. I don't know of other such effort since then. 
This led to rundata and some other objects pooling in turbine, and some 
changes of String concatenation to StringBuffer.append(). We also 
discovered a lot of duplicated initializations and similar stuff. It is 
always funny to see how big bugs can hide in code.

But the behaviour you are seeing looks more like the bug I pointed below 
or a bug in the hotspot compiler. Could you switch temporarily to jdk 
1.3.1_07 or 1.4.0_XX and see if the same happens? (According to reports 
in cocoon-dev, 1.4.0 does not have the StringBuffer bug)

> 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.
> 

If the problem is that some "bunches" of objects get into "old" space 
because they are pointed by persistent objects, then a juditious ammount 
of "= null" on recycling can help a lot. I've just checked 
DefaultJetspeedRunData and it is disposed properly (unless something is 
broken down in Turbine and it is not really disposed).

> - 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.
>>
>>
>> http://developer.java.sun.com/developer/bugParade/bugs/4724129.html
>>
>> 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 reloading.
>>


-- 
Santiago Gala
High Sierra Technology, S.L. (http://hisitech.com)
http://memojo.com?page=SantiagoGalaBlog



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


Re: Jetspeed Performance tips

Posted by Shan Gopalakrishnan <sg...@cisco.com>.
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.
>
>http://developer.java.sun.com/developer/bugParade/bugs/4724129.html
>
>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 
>reloading.
>
>
>--
>Santiago Gala
>High Sierra Technology, S.L. (http://hisitech.com)
>http://memojo.com?page=SantiagoGalaBlog
>
>
>
>---------------------------------------------------------------------
>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


Re: Jetspeed Performance tips

Posted by Santiago Gala <sg...@hisitech.com>.
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.
>>
> 

http://developer.java.sun.com/developer/bugParade/bugs/4724129.html

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 reloading.


-- 
Santiago Gala
High Sierra Technology, S.L. (http://hisitech.com)
http://memojo.com?page=SantiagoGalaBlog



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


Re: Jetspeed Performance tips

Posted by Santiago Gala <sg...@hisitech.com>.
Shan Gopalakrishnan wrote:
> 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.
> 

There are heavy bugs in the hotspot compiler en 1.4.1_01 (I'm not sure 
about Solaris, but it led to release of 1.4.1_02 some time ago). I've 
seen all the 1.4.1 VMs I have tested do very funny things (like 
disproportionate memory growth) under heavy load. I have stopped using 
1.4.1 for ant and maven, since they claim (sometimes) all memory and 
swap in my laptop, making it unusable for minutes, until I manage to 
kill the java processes.

I would either try with 1.3.1_07 or update 1.4.1 to latest. I strongly 
recomment to use 1.3.1 for stress testing (today) ;-)

Also, in tests I have done in dual PentiumIII with 1GB RAM, I observed 
that, with more than 50 simultaneous request, the performance degraded 
significantly.

I would recommend to design your system as a cluster (with session 
memory) to ensure that no more than, say, 10 requests will be processed 
in parallel for each VM. This is for small dual linux PentiumIII servers 
in the cluster (a much cheaper architecture than Solaris, BTW). If 
Solaris hardware allows, maybe the limit would be higher. But I would 
not try to squeeze every cycle from a VM.

Old (well tested) principles in Capacity Planning, coming from Mainframe 
ages, say that overall load of a system should never be planned to go 
over 60%.

> Thanks!
> 
> - Shan
> 

-- 
Santiago Gala
High Sierra Technology, S.L. (http://hisitech.com)
http://memojo.com?page=SantiagoGalaBlog



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


Object model for jetspeed/ turbine

Posted by Shan Gopalakrishnan <sg...@cisco.com>.
Does anybody has the object model of jetspeed / turbine and the flow of 
execution for rending the portal page.
appreciate any help on this. thanks in advance.

- Shan


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