Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Property Reference Pool Report shows non zero pruned value



The PropertyReferencePool Report shows a value which according to the System Administration Specialist (7.1) course, is not recommended.
In particular it states that the pruned field should be zero (0). User reports that on some of their systems the value of pruned is not zero.


Error Messages

PropertyReferencePool Report

Limit Current Requests Reused NotFound Pruned
30000 24025 41175204 41144210 30994 7184
Estimated size: 5M bytes

Steps to Reproduce

Not Applicable.

Root Cause

The default size of the PropertyReference cache is usually too small for medium size applications.


Create the following Dynamic System Settings.
Owning ruleset Setting purpose Value
Pega-Engine prconfig/collections/mru/PropertyReference/instancecountlimit/default 150000 (*)
Pega-Engine prconfig/collections/mru/LowerCase/instancecountlimit/default     20000 (**)
Pega-Engine prconfig/collections/mru/UpperCase/instancecountlimit/default 20000 (**)

 (*) Initial value that can be increased later on if necessary.
(**) It is recommended to increase the LowerCase and UpperCase cache sizes when the PropertyReference cache is increased.

Provided values come from the Pega 7 Platform cache and alert optimizations section contained in the following document available online:

Once completing the process mentioned in the restart the system to get these changes reflected.
Run the system for good amount of time then check the Pruned value again.

Suggest Edit

Published July 2, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us