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.
LinkedIn
Copied!

Use the MyAlerts tool to unit-test performance of one rule

 This presentation is part of the Designing and Building for Performance Self-Study Course.

 

Transcript

While PRPC's design time warnings are very powerful and very instructive, it is not possible to detect all performance related issues by simply looking at the structure of the rules and the database.   It is important to determine if the rules, when run, actually behave as expected.  PRPC has a built-in monitor, called alerts, that look for certain performance related behaviors of components and checks them against pre-set thresholds to see if they are performing outside of the norm.

When unit-testing rules, particularly activities and flows, check if any of these alerts are being generated.

To check for alerts, select the MyAlerts selection from the Tools menu.  The alerts generated for your session will be listed.

The "Alert Type" columns correspond to Pega alert codes. For example, the Browser Interaction Alert Type corresponds to Pega alert code PEGA0001.

The "Value" column provides a measure of the elapsed time in seconds that triggered the alert.  If there are several alerts, you should focus on those that are most severe and most prevalent.

There are over 20 different types of alerts, with the most common four alerts being:

  • DB Time (PEGA0007)
  • Browser Interaction (PEGA0001)
  • DB Bytes Read (PEGA0004)
  • Connect Total Time (PEGA0020)
Did you find this content helpful?

Have a question? Get answers now.

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