Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

How to estimate the memory required for pages

Updated on September 13, 2021

Summary

Is there a way to estimate the memory required for a page?

Suggested Approach

There are two ways to estimate this value.

Performance tool

The Performance Analyzer tool (PAL), accessible from the portal's Tools tab, includes in its Thread section a value in bytes for Requestor Clipboard Size. This value represents the total size of the clipboard. You could run PAL against your clipboard at various points in an application (before and after the page is populated), and checking the size difference, to estimate size required to support the page. .

Private API function

The PegaAPI interface of com.pega.pegarules.priv includes a Java method estimatePageDataSize which, given a page as parameter, returns the size of the page. See the V4.1 PublicAPI Javadocs  This method is for diagnostic purposes only, and in non-production environments only, as it depends on private Java classes and methods.

Note: Beginning with V4.2SP2 SmartBuild, Java classes in the "priv" package are not included in the PublicAPI Javadocs.   Code in the "priv" packages is subject to change from release to release, without notice, and is intended to support rule-assembly generated Java and other internal capabilities.   Use of private methods by Pega-supplied applications, frameworks, and/or customer configurations is NOT recommended because of upgrade considerations.

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us