Filter
Top Products
80
WEBSPHERE PORTAL V6.1 TUNING GUIDE
com.ibm.wps.pe.portletentity
Default size: 10000, default lifetime: 5800, usage pattern: regular.
This cache contains configuration for portlets on pages (portlet instances, shared and
per-user). It scales with the number of pages defined in your portal, the number of
portlets on the pages and the number of portlet instances that have been personalized
by users. The cache is accessed many times during portal page rendering. In so far it is
important that the most relevant portlet entities are cached. Creating a cache entry
involves a single database lookup. An entry into the cache is fairly small.
Example: In a portal with 500 pages and on average three portlets per page, the optimal
cache size would be 1500 to store all possible portlet entity data in the cache, if users
are not allowed to personalize the portlets. If the portal has 100 users that are logged in
concurrently and these users have personalized 50 portlets on average, the required
cache size to cache all data would be 6500. These numbers give the maximum number
of entries to the cache. Typically for this cache it is not required to have all portlet entities
in memory, because most users will not view all pages so that not all personalized data
must be loaded. The most frequently accessed un-personalized portlet entities should fit
into the cache, though.
com.ibm.wps.services.cache.cachedstate.CachedStateServiceCache.cache
Default size: 50000, default lifetime: 7200, usage pattern: typically regular.
This cache stores session-scoped data in the portal context and is used by various
portal components. This cache scales linearly with the number of active sessions in the
system and the number of portal components using this cache for data retrieval. The
usage pattern, access times, entry creation costs and entry memory sizes depend on
the portal component using this cache and cannot be stated in general.
wp.xml.configitems
Default size: 1000, default lifetime: infinite, usage pattern: regular.
This cache stores XML Access configuration items. It is used only during XML Access
processing. The entries resemble references between nodes in the XML Access
document. Especially when working with complex XML files, usually used for imports or
Release Builder processes, it can be beneficial to increase the cache size. The cache
will be cleared after XML processing is completed. Reloading a cache entry involves one
database query. Entries in the cache are medium-sized.
PortletMenuCache
Default size: 200, default lifetime: infinite, usage pattern: regular.
This cache contains portlet menu trees for all portlets that define their portal menu as
global, meaning identical for all users. The portal functionality that utilizes this cache is
deprecated with WebSphere Portal Version V6.0.