Heath Borders wrote: >For some reason, our pages that use Tiles don't perform anywhere near >as well as those that don't use tiles. > >I've been trying to figure out the performance issues, but I'm stuck. > >I've basically taken all of the code out of our layouts, so that all >of the same layouts are getting called, but there is no code in them >but the includes I need. > >The performance problem is really only an issue when we need to render >large (500+ rows) tables on a particular page. It takes the page up >to a minute to load in IE 6 using tiles, but the load is almost >instantaneous without tiles. > >Obviously, for developer productivity and maintainability, we really >love Tiles and want to continue using it, but we can't ignore these >performance issues. > >Does anyone have any ideas? > > > Due to the creation of Jsp fragments in a page, the first time is slow. But after that, it is very decent due to cache. We found it is much better than many other portal page assembling engines (either proprietary or open sources). Another thing needs to consider for performance is tried to avoid deep nested tiles. We try to achive 1 tile level of insertion and attribute processing. This means a large definition for the base template and all fragments are done with Jsf. Within each fragment, we try to be simple and do not have too many layers of tables and tags. This means some work may be required to strip unneccessagy layer of off-the-shelf UI components. You have to do it anyway for any serious work. Off-the-shelf components are only used to demonstrate the technology.
Hope these tips may help. BaTien DBGROUPS
