Do not use many transactions while serving one HTML page 5. USE CACHING (caching is easy to set up with hibernate) 4.
Reduce number of round trips to database to fetch data (Ex: RowFetchSize in JDBC, join queries, insert batch and retrieve generated keys via result sets in one round trip, etc) 3. Since I posted this we've moved to RichFaces which isn't really a bridge in the same way, it's more just a js library on the front and ways to connect with it on the back. Use indexes on database tables appropriately 2. Also ICEFaces is more than just a js library, it's an AJAX bridge, a nice idea but when things like this come along it starts to fall down. Review your code you might be calling same functions repeatedly which could have been called only once Hibernate, EJB and back-end performance tips 1. Avoid constructing and destroying objects in a loop. Do not over complicate EL expressions, code them in Java in backing bean 13. Consider using Web Remoting in some cases vs ajax4jsf for simple things (ex: dependable dropdowns) 12. Use java StringBuilder vs StringBuffer and + operator 11. Choose appropriate java collection based on access method (direct, sequential, by key) 10. Choose wisely between client side and server side in components such as tabs, collapsible panels, etc 8. Consider immediate=true attributes on elements where you do not need validation 7. Check documentation on ajaxOnly and relevant attributes 6. When using ajax4jsf you can sometimes reduce APPLY REQUEST VALUES JSF phase (which might be significant when large form with many inputs is submitted). Fancy ones are usually very slow especially in IE. Very often those render slow in browser cause of JavaScript in them, and not because of JSF server side RENDER phase. Avoid components which use have JavaScript on client side unless you tested them carefully for their client side performance. Try different methods to render same content (Ex: rendering tables with ui:repeat vs h:dataTable) 4. With many components on the page will help you to identify which one is performance killer 3. Tomahawk (check their recommendation about StreamingAddResource, t:documentBody, t:documentHead, t:document) 2. Make sure that your jar files contain XSD schemas and DTDs you refer in you XML configuration files especially Seam XSD (to prevent fetching them from Internet) Javassist performance optimization settings for Seam Performance of third party JSF component libraries 1. JRockIt JVM should perform better than Sun's one. Check your JVM setting make sure memory settings are adequate for your application. Myfaces Trinidad(ADF) wiki homepage (Oracle ADF donated to the Apache community and. You usually need to install additional DLLs or shared libraries for that, check app server documentation and warnings on start-up. JSF Sandbox homepage (an extension component library of jsf-ri). In production JBoss server turn off Seam DEBUG level logging which is turned on by default in JBoss log4j configuration It is quite excessive and goes into JBoss server log (you do not see it on console) Use Native I/O on your application server.
0 kommentar(er)
