LinkedIn
Copied!

Table of Contents

Garbage collection and memory management

Version:

Only available versions of this content are shown in the dropdown

The tactics and details of the garbage collection capability in your Java Virtual Machine (JVM) differ among JVM implementations from vendor to vendor. If garbage collection is not run often enough or is not successful enough at recovering unneeded memory, the JVM can fail with an out-of-memory exception. This could indicate a design or implementation flaw or that demand for virtual memory under the current workload exceeds supply.

The Pega-RULES agent periodically forces some memory segments to be available for garbage collection, using the standard activity Code-.SystemCleaner.

Minimizing memory demand

Each requestor clipboard occupies virtual memory. Best practices for clipboard management include:

  • Releasing pages that are no longer needed with the Page-Remove method.
  • Limiting the maximum number of instances retrieved by an Obj-Browse method or a report definition rule.
  • Retrieving only needed properties in an Obj-Browse method, Obj-List method, or a report definition rule.

Using the Performance tool, you can monitor the size of your clipboard in bytes.

PEGA0028 Alerts

If garbage collection completes but fails to produce enough results, the system adds an alert of type PEG0028 to the Alert log.

PegaRULES Log Analyzer

You can use the PegaRULES Log Analyzer, a standalone Web application available from the Pega Exchange, to analyze GC logs. See the Pega Community article Understanding the PegaRULES Log Analyzer.

Additional resources

JVM settings can affect the performance of your system. For information about JVM settings, use the Installation Guide for your platform, and see the Pega Community article JVM configuration best practices.

Have a question? Get answers now.

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