Tune cache for the repository service
You can tune the cache for the repository service. There are various sizing properties that can be set for local memory and disk resources. Settings can be unique on each dispatcher.
The following table provides a description of the types of cache
that can be tuned for the repository service.
| Parameter | Description |
|---|---|
| Maximum number of seconds reports and report elements can exist in the cache | The maximum number of seconds that a report can exist in the cache, regardless of how often it is used. After a report expires, it is retrieved from the repository instead of the cache. The default value is 20 minutes. A value of 0 means that the report is not saved in the cache. |
| Maximum number of reports and report elements that can overflow to disk | The maximum number of cache entries in to be kept in local memory. The default value is 100 entries. A value of 0 means that there is no limit to the number of items held in local memory. |
| Maximum number of reports and report elements that can be stored in memory | The maximum number of cache entries that can be written on the local disk. When the memory cache reaches the limit the items overflow to the local disk. The default value is 1000 reports and report elements. A setting of 0 means that there is no limit to the number of items written to disk. The entries are written to the data files location defined in IBM® Cognos® Configuration. |
The repository service uses the advanced setting repository.maxCacheDocSize to specify, in megabytes, the maximum size of each report output that can be stored in the cache. Outputs that are larger than the specified size are not cached and must always be retrieved from the repository or Content Manager. The default value is 10. You can specify this advanced setting individually for a specific repository service or a dispatcher, or globally for the whole IBM Cognos environment. For more information, see Advanced settings configuration.