To retrieve data from Performance Dashboard, the PPM server supplies a cache that provides the data more quickly for repeated queries by a Performance Dashboard and Management views.
Example: Performance Dashboard cache structure
You can adjust the cache in the keyindicator_settings.properties file in <installation directory>\ppmmashzone\server\bin\work\data_ppm\config\<client>.
Extract from the keyindicator_settings.properties file:
#----------------------------------
# Options for scorecard cache
#----------------------------------
# Memory based scorecard results LRU cache size. A value of zero disables this
# cache!
# Valid values: '0' or greater
SCORECARD_LRU_CACHE_SIZE=100
# Memory based history of scorecard queries LRU cache size. This cache will be used
# for precalculation of scorecard results after a data import into PPM system.
# A value of zero disables this cache!
# Valid values: '0' or greater
SCORECARD_HISTORY_LRU_CACHE_SIZE=250
# Specifies whether memory scorecard cache accesses are logged. (Only
# relevant if LOG_CACHE is set to 'true'.
LOG_SCORECARD_LRU_CACHE=false
The SCORECARD_LRU_CACHE_SIZE setting determines the number of query results of the dashboards held in the memory-based cache. If there is a large number of queries in a Performance Dashboard, the value for this setting should be increased to guarantee that the cache functions efficiently.
The history cache stores the last Performance Dashboard queries. The SCORECARD_HISTORY_LRU_CACHE_SIZE setting specifies the number of query results to be included in cache pre-calculation. This kind of cache precalculation is, for example, triggered after data import via runppmimport. It is advantageous to have a history cache larger than the LRU cache because also the PPM server accesses cache pre-calculation. The cache size of the PPM server is not limited.
Database-based cache
The Performance Dashboard history cache is memory-based, i.e., after restarting the PPM server the cache is empty and the PPM server calculates all queries again. By specifying the -savepchistory option of the runppmadmin command line program, you can save the history cache in the database before terminating the PPM server. Already existing cache content will be overwritten or deleted. Alternatively, you can use the -addpchistory option. In this case, the database is updated or extended with the history cache contents.
By default, the PPM server is configured for using caches (both USE_KI_CACHE and AUTO_FILL_CACHE keys of the client-specific configuration file Keyindicator_settings.properties with the value true), so that after starting the PPM server, the history cache is automatically filled with the content previously saved in the database when Performance Dashboard queries occur You can load the database-based cache into the history cache by explicitly specifying the -fillcache option of the runppmadmin command line program.
To delete the database-based cache, call up the runppmadmin command line program using the -clearpchistory option.