Filter
Top Products
76
WEBSPHERE PORTAL V6.1 TUNING GUIDE
wsrp.cache.servicedescription
Default size: 150, default lifetime: infinite, usage pattern: regular
This cache contains service descriptions of WSRP producers. It is used on the
consumer side. It scales with the number of WSRP producers integrated into the
consuming portals; there is exactly one description per producer. The service description
is generated using all the portlet descriptions from the producer portal plus some
additional data. Hence a service description can be large in terms of memory
requirements. Rebuilding the description requires several roundtrips and is an expensive
operation. Cache entries are rebuilt if a user clicks the ‘Browse’ button in the WSRP
administration portlets. This leads to a refresh of all service descriptions of all producers.
This cache is only used during WSRP administration.
wsrp.cache.portlet.instance
Default size: 2500, default lifetime: 3600, usage pattern: regular.
This cache contains the proxy portlet instances on the WSRP consumer side and is only
used there. It scales with the number of integrated remote portlets multiplied with the
number of users having their own customizations of portlet preferences for these remote
portlets (portlet settings for legacy portlets respectively). Creating an entry for the cache
involves one multi-line database query. The size of a cached entry depends on the
number of parameters associated with the portlet. Hence the size ranges from small to
fairly large.
wsrp.cache.producer.user
Default size: 5000, default lifetime: 3600, usage pattern: multiple object types.
This cache contains the descriptor of the producer and context information between
users and producers. It is used on the consumer side. It scales with the total number of
active users accessing remote portlets of these producers, i.e. as a maximum the
number of producers multiplied with the number of active users accessing them plus the
number of producers. Recreating cache entry is fairly expensive. It involves some DB
queries and in-memory operations. Therefore the session timeout should not be higher
than the lifetime of entries in the cache. Cache entries are explicitly invalidated during
user session destruction.
wsrp.cache.portlet.window
Default size: 2500, default lifetime: infinite, usage pattern: regular.
This cache contains a WSRP specific wrapper on a WebSphere Portal portlet entity
object. It is used on the producer side. It scales with the number of provided portlets and
the number of occurrences of these portlets on consumer pages. Recreating cache
entries is rather cheap and typically only includes in-memory operations. An entry into
this cache is fairly small. This cache is accessed very during a request.