PPM Support Tip: HP PPM Center White Paper - Understanding and Tuning the Cache
HP PPM Center White Paper - Understanding and Tuning the Cache
Since PPM 9.31, the cache manager is changed. All cache configuration defined in server.conf is deprecated and not used anymore, now you should use cache.conf to configure the cache:
Conversion from legacy cache to new cache.
All the legacy caches listed in kRunCacheManager.sh but one (Scoring Criteria) have been converted to new cache.
All these caches are now configured from cache.conf, and their parameters in tune.conf (or server.conf/admin console) have been deprecated and are not used anymore.
Simplification of new cache configuration
Some parameters in cache.conf have been removed in an attempt to simplify cache configuration.
•The only parameter that can be tuned for all caches is the cache size (parameter "maxSize").
•Parameters "maxAge", "maxIdleTime", "resolver" and "stalenessCheckGraceInterval" have been removed.
•Parameter "distributed" is inferred automatically based on whether a staleness check in defined (distributed = false) or not (distributed = true).
•Cache is automatically set to disabled if maxSize = 0.
A staleness check has also been added for request types and table components; even though it’s not enabled by default, if one relies on direct DB updates to modify request types or table components, it’s preferable to enable the staleness check rather than disable the cache. Staleness check will only work if column LAST_UPDATE_DATE is modified during data update.