IBM 6.1.X manual Com.ibm.wps.model.factory.ContentModelCache.isolated

also adds to the time it takes to rebuild a cache entry. Building the content model is done incrementally as required for the current request; the model is not built at once. Depending on the size of the model also the memory requirements vary. The more pages a user can access and has accessed already during the current session the larger the cache entry, ranging from medium to very large. A cache entry typically is composed of references to other cached and shared objects. Hence an entry size is not made up by the number of page and all subordinate objects but only contains references to these.

com.ibm.wps.model.factory.ContentModelCache.isolated

Default size: 1000, default lifetime: infinite, usage pattern: regular.

This cache contains the administrative content models. There is one entry for every user doing administrative work at a certain point in time. In so far the number of entries in this cache typically is much lower than in the other cache. But for this cache you should make sure that no cache entries of active users are evicted. Compare with the content model run-time cache for all other information.

com.ibm.wps.model.factory.NavigationSelectionModelCache.live

Default size: 1000, default lifetime: infinite, usage pattern: regular.

This run-time cache contains the navigation selection models used by portal users. There is one entry per user session. The cache should be large enough to hold all these models for the active users. An entry in the cache has the maximum lifetime of the corresponding user session, i.e. entries are removed at the end of the session. Creating a cache entry is less expensive than creating a content model cache entry. Typically all required information is in memory, but accessing the database might be necessary. In comparison to the content model cache creating an entry for the navigation selection model cache is much cheaper. In addition also the in-memory size of elements in this cache is much smaller since this type of model references fewer objects.

com.ibm.wps.model.factory.NavigationSelectionModelCache.isolated

Default size: 1000, default lifetime: infinite, usage pattern: regular.

This cache contains navigation selection models used by administrative users. The details given for the administrative content model cache also apply here.

com.ibm.wps.model.factory.URLMappingCache.live

Default size: 50, default lifetime: infinite, usage pattern: regular.

This cache is the run-time model cache for the URL mappings defined in your portal installation. It should be large enough to hold all URL mappings defined in your system. Creating an entry to the cache involves reading one entry from the portal database. A cache entry is fairly small in size.

7 2

W E BS P HE R E P O R T AL V 6 . 1 T U N I N G G U I D E