Server cache tuning parameters
File config.xml contains cache parameters for PolicyCenter. Access this file from Guidewire Studio at .
|
Parameter |
Description |
|---|---|
|
|
The number of seconds between refreshes of the exchange rates cache. PolicyCenter uses this specialized cache for exchange rates only. |
|
|
Time, in minutes, that PolicyCenter considers cached objects active. You can think of this as a period in which PolicyCenter is heavily using an item, for example, how long a user stays on a screen. The cache mechanism gives higher priority to preserving these higher-use objects. Set |
|
|
Boolean value that specifies whether to collect detailed
statistics for the global cache. Detailed statistics are data
that PolicyCenter collects to
explain why the caching mechanism evicted items from the cache.
PolicyCenter collects basic
statistics, such as the miss ratio, regardless of the value of
Guidewire sets the value of
If the GlobalCacheDetailedStats parameter is
set to At runtime, use the Management Beans screen to enable the collection of detailed statistics for the global cache. |
|
|
Time, in minutes, since the last use of a cached object before PolicyCenter considers the object eligible for reaping. This can be thought of as the period during which PolicyCenter is most likely to reuse an object. An evict timeout mechanism removes old objects from the cache.
Once per minute, a thread evicts cache entries that have not
been used for a period equal to or greater than
|
|
|
The number of seconds between refreshes of the groups cache. PolicyCenter uses this specialized cache for group-related data only. |
|
|
Maximum amount of heap space used to store cached entities,
expressed as a number of megabytes. This parameter supersedes
the value of At runtime, you can use the Cache Info or Management Beans screen to modify this value. |
|
|
Maximum amount of heap space used to store cached entities, expressed as a percentage of the maximum heap size. |
|
|
Time, in minutes, after which PolicyCenter considers an object in the cache stale if it has not been refreshed from the database. A stale timeout mechanism ensures that the server does not use excessively old object entries. An object is stale if it has not been refreshed from the database within a configurable amount of time. Upon accessing a cache entry, the server calculates the duration since the object was last read from the database. If that duration exceeds the stale time, the server refreshes the cache entry from the database. To avoid increased complexity, PolicyCenter prefers this mechanism over evicting objects upon stale timeout. At runtime, you can use the Cache Info or Management Beans screen to modify this value. |
|
|
This parameter denotes a period of time, in minutes, that PolicyCenter uses for two purposes:
|
|
|
The number of seconds between refreshes of the script parameters cache. PolicyCenter uses this specialized cache for script parameters only. |
|
|
The number of seconds between refreshes of the zones cache. PolicyCenter uses this specialized cache for zones only. |
See also
