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

High memory utilization with summary type report definition



Developer created a summary type report definition with a large number of group by columns, and observes very high memory utilization during the report execution.

Error Messages

Not Applicable.

Steps to Reproduce

Run a summary type report definition having large number of group by columns, which retrieves thousands of records (large dataset).

Root Cause

The root cause of this problem is software use or operation error.
A nested page structure will be generated for the groupings, by the report definition. 

Report definition (summary type) with high numbers of "group bys" for the columns generate a large amount of virtual memory overhead.
This is exacerbated in cases where the order of the groupings is not "most general" to "most specific", as more nodes are generated in the nested page structure.


Pega recommends user to review the groupings and eliminate any unnecessary ones, and reorder the remaining ones if possible to reduce the overhead. 
For example, pyID is not a good candidate for a group by (or) a first group by, as it will always give a group of 1.


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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