Question
Asurion
US
Last activity: 19 Apr 2017 9:24 EDT
PEGA0017 in Dev
We get a lot of PEGA0017 alert in dev environment. The system get really slow and we have to recycle to bring it back to normal. I read in article that we have to increase the cache size limit for this to be fixed.
prconfig/collections/mru/propertyreference/instancecountlimit/default
where i can see the this cache details in sysmgmt ? and how to find the optimum cache limit for a environment.
***Updated by moderator: Lochan to add Categories***
Accepted Solution
JP Morgan Chase
US
I think "instancecountlimit" is a env setting in prconfig or DSS.
SMA > Advanced > Rule Cache Management > "Instances" value is the cache size consumed by your app.
JP Morgan Chase
US
You can check in SMA > Advanced > Rule Cache Management > "Instances" value.
You can follow the below steps to get an idea..
1) start your app
2) Run the system covering all your major flows, screens, reports and create/resolve your work objects. Run the system as much as to cover frequently scenario's.
3) Clear the cache from SMA > Advanced > Rule Cache
4) Repeat step 2 again
5) Go back to SMA > Advanced > Rule Cache > Check the "instances' value
This value is the size of rule cache required. if its greater than the instancecountlimit try update the value and repeat the step 2 again to see if there is an improvement.
Accepted Solution
JP Morgan Chase
US
I think "instancecountlimit" is a env setting in prconfig or DSS.
SMA > Advanced > Rule Cache Management > "Instances" value is the cache size consumed by your app.