We are running into similar concerns with our implementation of JSF.
Can you provide which profiler tool you used?
We have noticed an increase of heap usage of late (cause out of memory exception in our production environment) which has required us to increase the amount of memory we are allocating to the heap. We are using Spring + Hibernate running on WebSphere 6.1. For JSF we are using apache MyFaces 1.1.5 and RichFaces 3.1.1. We are using session to hold information and placing that on the server. We tried to use the client but it was way to much and caused some other issues.
We are in the process of looking at what it takes to tune JSF, hence the interest in which profiling tool you used. We just started this research.
We are also exploring going with Spring MVC and dropping JSF all together. JSF has cause a bit of an issue with WebTrends and seems to drive up development estimates on GUI development.
TIA for any feed back you provide
suhasw1 wrote:
Please feel free TO REPLY to the group for this so all of us can benefit. Appologies about yesterday's direction !!! -Mark
Hi All,
I have profiled my Spring 2.0 + Hibernate 3.0 + JSF 1.1 application. 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?
2) What are the best practices when one is using JSF witrh AJAX?
3) 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.
Thanks in advance,
Suhaas