Question

2
Replies
2262
Views
Close popover
pradeep pydi (pradeepp2840)
Verizon Wireless
PEGA SENIOR SYSTEM ENGINEER
Verizon Wireless
US
pradeepp2840 Member since 2017 20 posts
Verizon Wireless
Posted: June 21, 2017
Last activity: June 22, 2017
Closed

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

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.

System Administration
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.