"jetspeed1 is a real performance hog, when I tried it out early this year. Even with just one or two self-written simple portlets, it would eat memory and CPU, till my dual-p4-xeon with 2GB of memory gave very sluggish performance - rendering pages in 100's of milliseconds."
I think it depends on how you developed your portal. I have developed 3 enterprise portal with Jetspeed 1 for 2 fortune 100 companies. We used velocity as default template engine as it has better performance than JSPs. We have extended for parallel content loading and proper content and object caching based on provided JS1 and turbine cache. It is up and running as P1 application. It was pretty easy for new portlet developments, personalization , error/exception handling and scalablity. Average page loading is less than 40 ms with 13 portlets.
Only issue we had concerned was about not standard to jsr 168. |
java.net RSS Feeds
