wood burning stoves
The moose likes Portals and Portlets and the fly likes Performance considerations for Portlets? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Portals and Portlets
Bookmark "Performance considerations for Portlets?" Watch "Performance considerations for Portlets?" New topic

Performance considerations for Portlets?

Eric Schumacher

Joined: Jun 02, 2004
Posts: 20
I'm a performance/testing tools guy at a larger company. I do internal consulting on many many different types of applications. Because of this I can never get fully aquainted with the different technologies. One of my current projects is a new implementation of IBM's portal server and of course portlets. I'm looking for advice on things to look for or to target in performance testing the application that is specific to it's "portalness".

Does anyone have a short or long list of things to look at for Portal/Portlet performance? Things I am starting to look at are possible fragment caching in the portal and edge caching servers for static content. We are also looking at min/max thread settings and high speed skins where applicable.

Any thoughts?

Julien Viet

Joined: Nov 08, 2005
Posts: 5
Hello Eric,

before doing any caching by yourself you can try to leverage portlet caching that is built in any portlet container.

that will have the effect to cache the portlet fragment for 60 seconds. If any request target the portlet (render or action) then the cache will be invalidated and render will occur again.

Julien Viet<br />JBoss Portal Project Lead
Eric Schumacher

Joined: Jun 02, 2004
Posts: 20
Julien, Thanks. Exactly, we are looking at the built in caching for portlets using the descriptor (plus possible in portlet code for forcing expiration) and the IBM edge caching proxy.
I agree. Here's the link: http://aspose.com/file-tools
subject: Performance considerations for Portlets?
It's not a secret anymore!