Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Performance considerations for Portlets?

 
Eric Schumacher
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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?

thanks.
 
Julien Viet
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
Eric Schumacher
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic