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.

Multiple hardware and software components affect performance

Updated on September 22, 2020

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



Overall performance is a function of how each of the main components performs within an application, which in PRPC includes the following:

  • Browser
  • PegaRULES database server
  • Other systems accessed via connectors and services
  • Application server in which PRPC resides
  • Network each of these components uses to communicate

Each component has a capacity. When the load on that capacity approaches its limit, performance can suffer.

  • CPU can become a bottleneck when developers write inefficient processing logic.
  • The Application Server’s Java Virtual Machine (JVM) shows stress in terms of garbage collection overhead when too much memory (in the form of clipboard pages) is used.
  • When we send and/or receive too much data, pressure is placed on the network, the database, the browser, and the CPU combined.
  • Response time problems are created when an application that for each request requires too many separate data requests due to network latency. This is especially true in geographically disbursed architectures.

These capacity limitations should be considered when designing and creating PRPC rules. The PRPC application server component is in the ideal position to provide a load view on the application server and can also report the performance of the components with which it communicates.

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

Close Deprecation Notice
Contact us