Question
Verizon Wireless
US
Last activity: 22 Jun 2017 7:35 EDT
Production servers :high JVM GC time and the MRU cache limit value
Hi Team,
High JVM GC time has been observed recently for all the production servers and after analyzing the heap dump and the Pega alert logs, we could find references to com.pega.pegarules.priv.collections.map.ConcurrentMostRecentlyUsedMap.countingSortRemove and lots of PEGA0017 alerts
Please find the current DSS value and most recent MRU cache report details below.
| collections/mru/lowercase/instancecountlimit | 10000 | Dynamic System Setting |
| collections/mru/propertyreference/instancecountlimit | 500000 | Dynamic System Setting |
| collections/mru/uppercase/instancecountlimit | 10000 | Dynamic System Setting |
collections/mru/PropertyReference MRU Report Entry class: KeyedSoftReference
Current Target Limit Max Age(m) Drained #Drains Limited #Limits Maxed #Maxes Maint(s) HardToSoftCount SoftToHardCount SoftRefGCedCount
Hi Team,
High JVM GC time has been observed recently for all the production servers and after analyzing the heap dump and the Pega alert logs, we could find references to com.pega.pegarules.priv.collections.map.ConcurrentMostRecentlyUsedMap.countingSortRemove and lots of PEGA0017 alerts
Please find the current DSS value and most recent MRU cache report details below.
| collections/mru/lowercase/instancecountlimit | 10000 | Dynamic System Setting |
| collections/mru/propertyreference/instancecountlimit | 500000 | Dynamic System Setting |
| collections/mru/uppercase/instancecountlimit | 10000 | Dynamic System Setting |
collections/mru/PropertyReference MRU Report Entry class: KeyedSoftReference
Current Target Limit Max Age(m) Drained #Drains Limited #Limits Maxed #Maxes Maint(s) HardToSoftCount SoftToHardCount SoftRefGCedCount
529683 400000 500000 600000 10 80130276 5193 0 0 100001 1 1585 80230277 449989 77232142
PropertyReferencePool Report
Limit Current Requests Reused NotFound Pruned
500000 520091 2432211091 2350873377 81337714 81126342
Estimated size: 681M bytes
PropertyReferenceFactory Report
Reused TargetSize
273548952 144
Pool sizes
6,5,6,3,0,2,9,1,1,3,0,0,0,1,5,4
Please suggest.
Pegasystems Inc.
IN
Hi Pradeep,
Enclosed are the settings that are usually recommended:
|
<env name="conclusioncache/RuleFileBinary/minimumsize" value="5000"/> |
These settings increase the maximum limits on our in-memory caches so that age-based pruning is greatly decreased |
|
<env name="collections/mru/PropertyReference/instancecountlimit" value="100000"/> |
These settings increase the maximum limits on our in-memory caches so that age-based pruning is greatly decreased |
|
<env name="cache/instancecountlimit" value="15000"/> |
These settings increase the maximum limits on our in-memory caches so that age-based pruning is greatly decreased |
|
<env name="appcentric/shortcutsMru/instancecountlimit" value="30000"/> |
These settings increase the maximum limits on our in-memory caches so that age-based pruning is greatly decreased |
Thank you
Pegasystems Inc.
IN
In addition to my previous comment:
Initially, the rule cache limit is 3,000 entries. This count includes rules on "probation". Probationary entries contain only keys and usage counts, rather than the full rule content. If this cache limit is approached during system operations, older entries are discarded automatically to make room for newer entries, following the Most Recently Used (MRU) algorithm.
You can change this limit by adding a prconfig.xml setting similar to:
<env name="cache/instancecountlimit" value="nnnnn" />
Memory consumed by this cache is not available for other JVM operations. To see the size in entries and bytes of this cache, select Designer Studio > System > Operations > System Management Application, select a node, and click the Memory Management menu item. Look for the row labeled Rule Instance in the Cache grouping.
Note: When required in special situations, your activity can call the PublicAPI function PRThread.setCacheEnabled(false) to disable rules caching temporarily for the current requestor.
In addition to my previous comment:
Initially, the rule cache limit is 3,000 entries. This count includes rules on "probation". Probationary entries contain only keys and usage counts, rather than the full rule content. If this cache limit is approached during system operations, older entries are discarded automatically to make room for newer entries, following the Most Recently Used (MRU) algorithm.
You can change this limit by adding a prconfig.xml setting similar to:
<env name="cache/instancecountlimit" value="nnnnn" />
Memory consumed by this cache is not available for other JVM operations. To see the size in entries and bytes of this cache, select Designer Studio > System > Operations > System Management Application, select a node, and click the Memory Management menu item. Look for the row labeled Rule Instance in the Cache grouping.
Note: When required in special situations, your activity can call the PublicAPI function PRThread.setCacheEnabled(false) to disable rules caching temporarily for the current requestor.
Propertyreference:
A property reference is a property of mode Single Value, Value List, Value Group, Page, Page List or Page Group that can operate to maintain what appears as an automatic copy of properties on another page. Property references can eliminate the need for copying the contents of one value or page into one or more other values or pages.
To define a propertyreference, select the Reference Property box on the Behaviour tab of the Property form.
Then use the Property-Ref method to link values from another page (known as the non-reference page) to a page of the reference property. Thereafter, changes to the non-reference page — through the Property-Set method, other methods, Declare Expression rules, and so on — also appear on the reference page.
For further information , please refer the below link:
https://community.pega.com/sites/default/files/help_v718/procomhelpmain.htm
Thank you
Hope this will help.