Question2Replies1476Views NAGENDRAN-1 Member since 2011 9 posts Asurion Posted: November 25, 2015Last activity: April 19, 2017 Closed Solved PEGA0017 in DevWe 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/defaultwhere 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*** System Administration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post 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. Posted: 4 years agoVenkata_D JP Morgan Chase replied to NAGENDRAN-1You can check in SMA > Advanced > Rule Cache Management > "Instances" value.You can follow the below steps to get an idea..1) start your app2) 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 Cache4) Repeat step 2 again5) Go back to SMA > Advanced > Rule Cache > Check the "instances' valueThis 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 Posted: 4 years agoVenkata_D JP Morgan Chase replied to Venkata_DI 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.