Performance Issue

[stormspire <st...@gmail.com>]

We are using Myfaces 1.1.5 SNAPSHOT + tomahawk-1.1.5-SNAPSHOT +
tomahawk-sandbox-1.1.5-SNAPSHOT + facelets in websphere environment.
We have big performance issue, not only the response is slow, avg 6 seconds,
but also our application consumes lots of memory.
The max heap size for us is 512M, although it is slow, another application
with more users resided in the same app server doesn't have performance
issue, it's also using 512M max heap size.  That application is using
struts.

Right now we usually save state the whole bean, and using server side.  I
follow http://wiki.apache.org/myfaces/Performance quite closely. Is there
any other way to improve it?  I am considering switching to client state,
and add a compression on the state.  Anyone has already done it?
-- 
View this message in context: http://www.nabble.com/Performance-Issue-tf2884773.html#a8059829
Sent from the MyFaces - Users mailing list archive at Nabble.com.

Re: Performance Issue

[stormspire <st...@gmail.com>]

We have a memory constraint here, is there any one has done application
successfully with large pool of concurrent users?  We use statestate
extensively, and we save the whole bean usually, i doubt this is the problem
for us.  It doesn't scale very well.


Dennis Byrne wrote:
> 
>>one question: when the beans declared in faces-config are created?  upon
>>request?
>>When will the app server destroy beans inside server, only after session
>>expired according to application config?
> 
> The beans declared in faces-config are created and destroyed according to
> scope (none, request, session and application ) and access.  For example,
> a request scope bean is created upon first access and marked for garbage
> completion (provided no other references to it) at the end of the request. 
> Scope is configured in you faces-config file.
> 
>>> any other way to improve it?  I am considering switching to client
>>> state,
>>> and add a compression on the state.  Anyone has already done it?
> 
> Server side state saving is almost always faster than client side state
> saving, although it uses more memory.
> 
> Dennis Byrne
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Performance-Issue-tf2884773.html#a8070705
Sent from the MyFaces - Users mailing list archive at Nabble.com.

Re: Performance Issue

[stormspire <st...@gmail.com>]

one question: when the beans declared in faces-config are created?  upon
request?
When will the app server destroy beans inside server, only after session
expired according to application config?



stormspire wrote:
> 
> We are using Myfaces 1.1.5 SNAPSHOT + tomahawk-1.1.5-SNAPSHOT +
> tomahawk-sandbox-1.1.5-SNAPSHOT + facelets in websphere environment.
> We have big performance issue, not only the response is slow, avg 6
> seconds, but also our application consumes lots of memory.
> The max heap size for us is 512M, although it is slow, another application
> with more users resided in the same app server doesn't have performance
> issue, it's also using 512M max heap size.  That application is using
> struts.
> 
> Right now we usually save state the whole bean, and using server side.  I
> follow http://wiki.apache.org/myfaces/Performance quite closely. Is there
> any other way to improve it?  I am considering switching to client state,
> and add a compression on the state.  Anyone has already done it?
> 

-- 
View this message in context: http://www.nabble.com/Performance-Issue-tf2884773.html#a8059842
Sent from the MyFaces - Users mailing list archive at Nabble.com.