I am wondering if anyone has any general performance tips for RichFaces.
I've tried to cover some bases already (caching common, but rarely changing, data at application level; not doing complex logic in getters/setters etc), I am thinking more about things that can be done at the RichFaces or Web Application level (this is going to be hosted on Tomcat 6). For example; Neko vs Tidy parser, or data compression or what have you.
Links to articles/docs is more than good enough - I've been searching but it is like looking for one particular needle in a large pile of other needles!
Typical application bottlenecks are poor database connection handling and potentially overloading the Session. The web layer generation usually pales in comparison to these performance monsters.
Do you have evidence that performance is going to be a problem? I'd hate to see you spend time tackling a problem that might not exist?
Are you anticipating a processor bottleneck? Bandwidth bottleneck? Memory bottleneck?
Joined: Jun 09, 2009
Not anticipating major bottlenecks just now, trying my best not to hold any state on the server etc. And you right about the database, the logs show the web server sat about and twiddling its thumbs waiting for a response - unfortunately that is outside my control and I cannot do anything about it.
I was more thinking about general RichFaces config stuff that I might be aware of. I know that Trinidad can be configured to not process timestamp changes etc., just wondering if there were any general RichFace-type tips/standard practices.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com