Reports and performance
When an application first goes into production, its reports can run without issue and within established service-level agreements (SLAs). As the amount of application data grows, the report can run more slowly. Poor report performance can cause memory, CPU, and network issues. These issues can affect all application users, not just the user running the report.
To help you diagnose and mitigate these issues, Pega software generates performance alerts when specific limits or thresholds are exceeded. For example, the PEGA0005 - Query time exceeds limit alert helps you recognize when queries are inefficiently designed, or when data is loaded indiscriminately.
For more information about performance alerts, see the List of performance alerts and security alerts on the Pega documentation site.
Memory impact
Large result sets can cause out-of-memory issues. Applications place query results on the clipboard page of the users. If those pages are not managed, your application eventually shuts down with an out-of-memory (OOM) error.
CPU impact
Using complex SQL can also have a CPU impact on the database server. When the database is performing poorly, all users on all nodes are affected. Pega Predictive Diagnostic Cloud (PDC) can help you identify the issues. Your database server administrator can set up performance monitoring for the database server.
Network impact
Sending large result sets over the network can cause perceived performance issues for individual users, depending upon their bandwidth, network integrity, and network traffic. It is not a best practice to pull large data sets from the database onto the clipboard, but is always recommended to use pagination, and smaller datasets that are within the default size limit.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
Want to help us improve this content?