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.

Use four facilities to achieve good performance

Updated on September 22, 2020

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

 

Transcript

When designing a PRPC application, consider these four checklist items to ensure you address performance issues early.

  1. Design Time Warnings:  Be attentive to PRPC warnings. They indicate when something may not be quite right with one of your rules.
  2. Performance Alerts:  When unit testing, ensure rules run within the expected SLA time and they do not use system resources above certain pre-set thresholds.
  3. PAL:  Inspect the unit-tested run-time statistics of PAL to identify indications of abnormal usage.
  4. Application Functionality: Ensure there are no behind-the-scenes errors that may have performance implications.

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