at
this point).
Thanks
-Original Message-
From: Mark Struberg [mailto:strub...@yahoo.de]
Sent: Tuesday, October 18, 2011 4:58 PM
To: MyFaces Discussion
Subject: Re: My Faces Tunning
+1 mem is barely a problem these days.
Actually we are serving 60.000++ users per day without any mem
...@virtua.com]
Sent: Tuesday, October 18, 2011 11:31 AM
To: MyFaces Discussion
Subject: Re: My Faces Tunning
Hello David,
How large are your pages? Do you have several tabs each with nested tabs
and
lots of fields? Which component suite(s) are you using?
---
Kito D. Mann | twitter: kito99 | Author
[mailto:kito.m...@virtua.com]
Sent: Tuesday, October 18, 2011 11:31 AM
To: MyFaces Discussion
Subject: Re: My Faces Tunning
Hello David,
How large are your pages? Do you have several tabs each with nested tabs
and
lots of fields? Which component suite(s) are you using?
---
Kito D. Mann
A few thoughts:
- Set the NUMBER_OF_VIEWS_IN SESSION to 1 if your app does not support
the browser back button!
- try to reduce the number of components (e.g. conditionally controls
can be excluded at compile time via c:if or via dynamic includes instead
of visibleOnUserRole or rendered
@myfaces.apache.org
Cc:
Sent: Tuesday, October 18, 2011 9:36 AM
Subject: Re: My Faces Tunning
A few thoughts:
- Set the NUMBER_OF_VIEWS_IN SESSION to 1 if your app does not support
the browser back button!
- try to reduce the number of components (e.g. conditionally controls
can be excluded at compile
Subject: Re: My Faces Tunning
- Set the NUMBER_OF_VIEWS_IN SESSION to 1 if your app does not support
the browser back button!
And once a user opens another browser tab all will crash :(
The missing windowId support is really a pitty in the JSF spec, and we
currently think hard about how to solve
Hello David,
How large are your pages? Do you have several tabs each with nested tabs and
lots of fields? Which component suite(s) are you using?
---
Kito D. Mann | twitter: kito99 | Author, JSF in Action
Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting
Still (I know it is not an option) but if you need to reduce session
space JSF 2 is the way to go, the delta state saving can free a load of ram.
Werner
Am 10/17/11 10:58 PM, schrieb Scott O'Bryan:
Wow.. Looks like you've done a lot, but I personally think 5K is
unrealistic. Your right.
to how we are managing the backing
beans?
-Original Message-
From: Scott O'Bryan [mailto:darkar...@gmail.com]
Sent: Monday, October 17, 2011 4:58 PM
To: users@myfaces.apache.org
Subject: Re: My Faces Tunning
Wow.. Looks like you've done a lot, but I personally think 5K is
unrealistic
@myfaces.apache.org
Subject: Re: My Faces Tunning
Wow.. Looks like you've done a lot, but I personally think 5K is
unrealistic. Your right. Essentially JSF stores your component tree in
memory.
You MAY be able to enable client-side state saving which should free you
up some memory at the expense
,
strub
From: Tobias Eisentrager teisentrae...@googlemail.com
To: MyFaces Discussion users@myfaces.apache.org
Sent: Tuesday, October 18, 2011 10:46 PM
Subject: Re: My Faces Tunning
David,
Usually memory is the problem - but sometimes there are also CPU problems
BlackBerry)
- Original Message -
From: Tobias Eisentrager [mailto:teisentrae...@googlemail.com]
Sent: Tuesday, October 18, 2011 04:46 PM
To: MyFaces Discussion users@myfaces.apache.org
Subject: Re: My Faces Tunning
David,
Usually memory is the problem - but sometimes there are also CPU
[mailto:strub...@yahoo.de]
Sent: Tuesday, October 18, 2011 04:58 PM
To: MyFaces Discussion users@myfaces.apache.org
Subject: Re: My Faces Tunning
+1 mem is barely a problem these days.
Actually we are serving 60.000++ users per day without any mem problems (w 100
views/session ServerSide-StateSaving
All,
I am doing some investigation into how to shrink the amount of session
memory our JSF application is consuming on a per user basis.
We are using MyFaces 1.1.7 and Tomahawk 1.1.5 running on IBM Websphere
7.0 patch 19. (Not able to upgrade either of these items at this time)
IBM's
Wow.. Looks like you've done a lot, but I personally think 5K is
unrealistic. Your right. Essentially JSF stores your component tree in
memory.
You MAY be able to enable client-side state saving which should free you
up some memory at the expense of storing the entire view tree on the
15 matches
Mail list logo