Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=NmO4IrxxbTdx/6pTfb+yKaWCRmQ/RT9IP5+dDZoIcI8P73G9BxsetMFbp8rgmbkCkwigc6ZorANDtnx6zDf5Z/iB/K5x/xGFKZCot+1MPRke/u3l+6AiDrguG7VtCUXIgQQGDRsBxDXc84eCCpZxFnZvJY+zC2r+AQYXBTIy3sQ=;
References: <C291EADD2FB2694DA5097D3AF69A8D4225F6F59D@P-CORP-MSG-01.adesa.com>
 <4E9D2C6A.8080202@googlemail.com>
Message-ID: <1318924845.25650.YahooMailNeo@web27802.mail.ukl.yahoo.com>
Date: Tue, 18 Oct 2011 09:00:45 +0100 (BST)
From: Mark Struberg <struberg@yahoo.de>
Reply-To: Mark Struberg <struberg@yahoo.de>
Subject: Re: My Faces Tunning
To: MyFaces Discussion <users@myfaces.apache.org>
In-Reply-To: <4E9D2C6A.8080202@googlemail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

> - Set the NUMBER_OF_VIEWS_IN SESSION to 1 if your app does not support =
=0A> the browser back button!=0A=0AAnd once a user opens another browser ta=
b all will crash :(=0A=0AThe missing windowId support is really a pitty in =
the JSF spec, and we currently think hard about how to solve this (at least=
 in MyFaces).=0AUntil then all the stored views are shared accross all open=
 browser tabs.=0A=0AThe best thing you can do to reduse Session space is to=
 use ClientSideStateSaving=0A=0ALieGrue,=0Astrub=0A=0A=0A----- Original Mes=
sage -----=0A> From: Michael Heinen <mhn4dev@googlemail.com>=0A> To: MyFace=
s Discussion <users@myfaces.apache.org>=0A> Cc: =0A> Sent: Tuesday, October=
 18, 2011 9:36 AM=0A> Subject: Re: My Faces Tunning=0A> =0A> A few thoughts=
:=0A> - Set the NUMBER_OF_VIEWS_IN SESSION to 1 if your app does not suppor=
t =0A> the browser back button!=0A> - try to reduce the number of component=
s (e.g. conditionally controls =0A> can be excluded at compile time via c:i=
f or via dynamic includes instead =0A> of visibleOnUserRole or rendered che=
cks).=0A> - facelets instead of jsps=0A> - plain html tags where possible=
=0A> - short component ids=0A> =0A> Michael=0A> =0A> =0A> =0A> Am 17.10.201=
1 22:16, schrieb Boyd, David (Corporate):=0A>>  All,=0A>> =0A>> =0A>> =0A>>=
  I am doing some investigation into how to shrink the amount of session=0A=
>>  memory our JSF application is consuming on a per user basis.=0A>> =0A>>=
 =0A>> =0A>>  We are using MyFaces 1.1.7 and Tomahawk 1.1.5 running on IBM =
Websphere=0A>>  7.0 patch 19. (Not able to upgrade either of these items at=
 this time)=0A>> =0A>> =0A>> =0A>>  IBM's guideline is that the session siz=
e should be less then 5k -=0A>>  average around 2.5k in order not to impact=
 performance of the server and=0A>>  session replication.=A0 We are current=
ly using Memory to Memory but=0A>>  looking at moving to database as sugges=
ted by IBM.=0A>> =0A>> =0A>> =0A>>  Our site was running at about 35M per u=
ser.=A0 We changed the number of=0A>>  view states from 100 to 10 and that =
dropped it down to around 4M.=0A>> =0A>> =0A>> =0A>>  We have several backi=
ng beans which are currently session scope and are=0A>>  looking at changin=
g them to request scope.=0A>> =0A>> =0A>> =0A>>  I also found the following=
:=0A>>  http://www.econsulting.nl/images/pdf/Tuning%20JSF%20Applications-%2=
0J-Sp=0A>>  ring%202008.pdf which seems to have a lot of information concer=
ning how=0A>>  JSF handles certain content on the pages.=A0 This is still u=
nder=0A>>  investigation to make sure what is stated make sense.=0A>> =0A>>=
 =0A>> =0A>>  I have also read somewhere that regardless if the managed bac=
king bean=0A>>  is session or request scope is that the view state will sti=
ll have the=0A>>  bean and its content.=A0 So the view state size will not =
change.=A0 Looking=0A>>  for clarification on this one.=0A>> =0A>> =0A>> =
=0A>>  The questions is are others facing the same issue in which JSF=0A>> =
 applications tend to consume a lot of memory for a given users session?=0A=
>> =0A>> =0A>> =0A>> =0A>>  What are some of the best practices to reduce t=
his size if any or is=0A>>  this just the way when using JSF?=0A>> =0A>> =
=0A>> =0A>>  Issues with session replication on IBM WebSphere when running =
a JSF=0A>>  application?=0A>> =0A>> =0A>> =0A>>  What we see as a result of=
 this is that in the event a user hops to=0A>>  another server, the session=
 data is not present due to how large the=0A>>  data is and how long it tak=
es to replicate.=A0 User experience issues.=0A>> =0A>> =0A>> =0A>>  We had =
seen an issue in which it appeared that changes to the object in=0A>>  the =
session was not being updated correctly and have done some session=0A>>  ma=
nagement tuning in which we customize the settings so that all session=0A>>=
  attributes are written out.=A0 Looking at the .jar file it does appear=0A=
>>  that myFaces is making the call correctly when the contents of the=0A>>=
  object in the session changes.=A0 So WebSphere session listener should be=
=0A>>  picking up that change.=0A>> =0A>> =0A>