[ajug-members] **** SPAM ****

[Joe Sam Shirah]

    I noticed that the original poster posted the original message to the 
Chicago and Austin JUGs, with no replies.  It will be mildly interesting to 
see how far west he gets.  Of course, there's ninjava in Tokyo...


                                                         Joe Sam

Joe Sam Shirah -        http://www.conceptgo.com
conceptGO       -        Consulting/Development/Outsourcing
Java Filter Forum:       http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International?    http://www.jguru.com/faq/I18N
Que Java400?            http://www.jguru.com/faq/Java400

----- Original Message ----- 
From: "Joe Sam Shirah" <joe_sam at bellsouth.net>
To: <ajug-members at ajug.org>
Cc: <jaxjug at yahoogroups.com>
Sent: Thursday, March 19, 2009 10:47 PM
Subject: Re: [ajug-members] Tips on JSF Performance Tuning - RichFaces & 
MyFacesJavaServer Faces Implementations


>
>    Hi Suhaas,
>
>    Without any intent to be offensive, I really had to hold back on
> sarcasm.  To be brief, if one puts enough moving parts together, one can
> eventually get a mess and even impact performance.  To complicate matters, 
> a
> recent mail from one of your colleagues indicated something about running
> WebSphere with the reference JSF implementation.  If that's true, then you
> have three of them going on: IBM's, Sun's, and MyFaces ( oh my. )
>
>    I assume the
>
>> stuck with RichFaces 3.1 (based on JSF1.1) due to dependency on
>> Weblogic NetUI
>
> is due to using the Apache Beehive integration.  So, first question:  Can
> you do without that?
>
>> 1) Does putting beans in request scope would always have a better
>> performance over those set in session scope?
>
>    No.  It should (almost) always be more scalable.  They could have very
> serious performance issues if a lot of work or, say, database/network 
> access
> is involved in creation.  OTOH, if session scoped beans use too much 
> memory,
> you could be dead in the water.
>
>> 3) What are the best practices when one is using JSF witrh AJAX?
>
>    Not quite sure why you went 1, 3, 2, but when in Rome...   As always,
> depends on what you are doing, but avoiding as much of the life cycle as
> possible is a good thing.  RichFaces also has some queuing mechanisms plus
> regions that can be very helpful.
>
>> 2) We are considering switching to Server side state saving with no
>> serialization (MyFaces has configuration options for this). Does anyone
>> have
>> any experience with this?
>
>    Your pages should certainly load faster with Server side.  Again, 
> memory
> is impacted; that's the reason JSF provides the option.
>
>> 4) Also any idea what is the performance hit due to a PhaseListener and
>> AOP,
>> as both of them are applied to every request ?
>
>    Depends almost entirely on the amount of work done.
>
>> I would really appreciate if any of you could give me pointers to best
>> practices in JSF programming as regards performance tuning.
>
>    Google.  Email or forums are not particularly good places for
> non-focused tuning, which could take a book.
>
>    Overall, your project sounds like it could be fun and fulfilling, 
> except
> this:
>
>> Also during this part of development cycle we cannot switch to Facelets,
>> to
>> gain performance benefits.
>
> tends to say to me that you're not going to have the ability (in time or
> freedom) to really put things right.  Good luck,
>
>
>                                                         Joe Sam
>
> Joe Sam Shirah -        http://www.conceptgo.com
> conceptGO       -        Consulting/Development/Outsourcing
> Java Filter Forum:       http://www.ibm.com/developerworks/java/
> Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
> Going International?    http://www.jguru.com/faq/I18N
> Que Java400?            http://www.jguru.com/faq/Java400
>
> ----- Original Message ----- 
> From: "Suhas Walanjoo" <suhas.walanjoo at gmail.com>
> To: <ajug-members at ajug.org>
> Sent: Thursday, March 19, 2009 3:54 PM
> Subject: [ajug-members] Tips on JSF Performance Tuning - RichFaces &
> MyFacesJavaServer Faces Implementations
>
>
>> Hi all,
>>
>> I have profiled my  Spring 2.0 + Hibernate 3.0 + JSF 1.1. I also ran 
>> Yslow
>> for browser side optimization. It led me to think that the problem is 
>> more
>> to with JSF side of the application than the back-end side.
>>
>> We are stuck with RichFaces 3.1 (based on JSF1.1) due to dependency on
>> Weblogic NetUI (used for flow). From JBoss Jira I can clearly see, most
>> performance improvements as part of bug-fixing process, have gone into
>> RichFaces 3.2 (recommended to be used with Seam 2.1)
>>
>> Also during this part of development cycle we cannot switch to Facelets,
>> to
>> gain performance benefits.
>>
>> Here are some clarifications I am seeking
>>
>> 1) Does putting beans in request scope would always have a better
>> performance over those set in session scope?
>>
>> 3) What are the best practices when one is using JSF witrh AJAX?
>>
>> 2) We are considering switching to Server side state saving with no
>> serialization (MyFaces has configuration options for this). Does anyone
>> have
>> any experience with this?
>>
>> 4) Also any idea what is the performance hit due to a PhaseListener and
>> AOP,
>> as both of them are applied to every request ?
>>
>> I would really appreciate if any of you could give me pointers to best
>> practices in JSF programming as regards performance tuning.
>>
>> Regards,
>>
>> Suhaas
>>
>