-
1. Re: Performance issues with a Richfaces application
ilya_shaikovsky Sep 23, 2008 8:21 AM (in response to sathis.g)which app server you using?
-
2. Re: Performance issues with a Richfaces application
sathis.g Sep 23, 2008 8:40 AM (in response to sathis.g)We are running the application Tomcat 6.0.14
-
3. Re: Performance issues with a Richfaces application
ilya_shaikovsky Sep 23, 2008 8:49 AM (in response to sathis.g)ok.. I've asked because we have such issue as known for webSphere and this was a server trouble.
In your case all seems should be ok.. Inform us also about RF version and browser you've using.
Also please try script loading strategy defined as ALL. -
4. Re: Performance issues with a Richfaces application
sathis.g Oct 21, 2008 5:17 AM (in response to sathis.g)Sorry for the late reply..
But which Script Loading Strategy should ideally be used for better performance. According to the docs,the ScriptLoading strategy "ALL" turnsoff javascript compression.
What is the exact difference between the Strategy "ALL" and "Default" (not able to understnad what is given in the docs) -
5. Re: Performance issues with a Richfaces application
nbelaevski Oct 21, 2008 6:14 AM (in response to sathis.g)Hello,
ALL turns off runtime javascript compression because script files that ALL uses are already compressed.
Script and style resources are load on per-component base when DEFAULT is used, e.g. only the resources required by components currently present on the page are loaded.
ALL strategy loads aggregate script and style resources that were created by merging all existing component resources; that aggregate files are somewhat huge in size, but increase performance because the number of server requests decreases. Also if you do not have component C included in view A but use it in view B then switching from A to B won't trigger resources loading for C component if you use ALL.
I suggest that you try monitoring tool built into Eclipse/MS Fiddler tool/some network sniffer and check if resources are cached in fact or not. Maybe performance tester do not cache them for some internal reason?