Reports and performance

When an application first goes into production, a report may run with no issue and within established service-level agreements (SLAs). As the amount of application data grows, the report may 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 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 List of performance alerts and security alerts.

Large result sets can cause out-of-memory issues. The application places 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.

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. Autonomic Event Service (AES) and Predictive Diagnostic Cloud (PDC) can help you identify the issues. Your database server administrator can set up performance monitoring for the database server.

Sending large result sets over the network may cause perceived performance issues for individual users depending upon their bandwidth, network integrity, and network traffic.