Session/PageFlowScope memory optimisation
-----------------------------------------
Key: TRINIDAD-1848
URL: https://issues.apache.org/jira/browse/TRINIDAD-1848
Project: MyFaces Trinidad
Issue Type: Task
Components: Documentation
Affects Versions: 1.0.10-core
Environment: HP Unix , WebLogic 9.2
Reporter: Paul Lake
I would have raised this as an issue type of question but this option is not
made available so please let me know how I can pose a question if this is
incorrect method.
I am working with a multi-national company helping to optimize the use of
memory on their application servers. This investigation has concluded that the
web application that is implemented on these servers and using Trinidad version
1.0.10 is not configured in an optimal manner. We have the means to measure the
memory occupancy accurately and can observe the effect of changing some of the
Trinidad settings as explained below.
The application is a very straightfoward web implementation and does not need
to support functionality that allows the users of the solution to traverse
backwards using the browser control. Consequently some of the functionality of
Trinidad can be safely disabled to avoid unnecessarily high use of memory. The
application is used by high user populations and the object of the
investigation is to determine how many users can be supported by the
application server (assuming no other contraints).
Having done some research including reading some previous discussion threads
around this subject I feel we could do with some guidance as to how to
configure the web application for optimal effect and I am hoping you can assist
us.
These are I believe the relevant configuration settings together with their
current settings:
In web.xml:
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
</context-param>
(If this had been server (the default) other settings would also be relevant)
<context-param>
<param-name>
org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION
</param-name>
<param-value>1</param-value>
</context-param>
<context-param>
<param-name>org.apache.myfaces.trinidad.CLIENT_STATE_MAX_TOKENS</param-name>
<param-value>1</param-value>
</context-param>
We believe that setting in
org.apache.myfaces.trinidadinternal.application.VIEW_CACHE may be implicated
but do not fully understand the purpose of this item.
In trinidad-config.xml:
<page-flow-scope-lifetime>1</page-flow-scope-lifetime>
We have noticed that changing this latter value down from its default of 15
compromises the application intermittently particularly during PPR operations
and we do not understand the reason for this. The failure is associated with
the loss of data in the pageFlowScope.
So to repeat this is a fairly simple application with a high number of
concurrent users and therefore optimising the session size is an important
consideration.
If you could please take the time to explain how we can configure the solution
for optimal effect (minimising memory whilst maintaining full functionality) I
would be very grateful.
Thank you.
Paul
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
