-
1. Re: JSF memory problems
wildrook Jun 8, 2008 12:29 PM (in response to wildrook)I think that I've already have an answer how to use JSF + Richfaces solutions for the sites with many concurrent users.
1. Buy memory, nowdays it is cheap. But I'm one of those who played Doom only on 4 Mbytes and it "flies" comparing with JSF sites on 4Gbytes.
2. Develop a filter+cache that manages org.ajax4jsf.application.AjaxStateHolder objects, in case of many users simply serialize all session objects and save it to the disk. I'm not sure that it will work but I will try to implement in the nearest future.
Any other ideas? I was very suprising that everybody talk about JSF but don't understand that JSF only works with "Hello World" examples or I'm wrong? JSF views, StateHolders and xml parsers really use a lot of memory and cpu: 20-30 Mbytes to send 10Kbytes of rendered page, this is simply shock me.
I will be very gratefull if somebody exaplain me where I mistake. By the way what hardware is used for Richfaces Demo site and what is the average load, concurrent sessions? -
2. Re: JSF memory problems
nohacks Feb 21, 2009 10:15 PM (in response to wildrook)Did you ever find an answer to your memory problem? We have a site that is going to go live soon too...we expect a heavy load of users as well.
Phil -
3. Re: JSF memory problems
babazs Oct 19, 2010 3:41 AM (in response to nohacks)I have the same problem in the end of 2010 year.
Did somebody find any solution for this??
Thank you any answer!!
-