Skip to main content
This content is now archived and is no longer updated. Progress is not calculated. Pega Cloud instances are disabled, and badges are no longer awarded. Click here to continue your progress in the latest version.

Performance testing tools

Performance Testing

Performance is an important aspect of any system. The perceived quickness of the system often measures user satisfaction and business value. Pega provides a full suite of tools to monitor and address performance. You use these tools during development to ensure that your configuration performs optimally.


The Performance landing page provides access to the three performance tools: Performance Analyzer (PAL), Database Trace, and Performance Profiler. These tools are also available by clicking Performance tool in the toolbar. You can learn more about the performance tools in the help topic Understanding system resources. Use the performance tools to collect performance statistics. Performance statistics can help you distinguish between performance issues that arise in the Pega Platform server, the database, or external systems called. In all cases, the statistics can help you determine how to improve performance.

Performance Analyzer (PAL)

Pega Platform™ always gathers cumulative resource statistics. Use the Performance Analyzer (PAL) to understand the system resources consumed by processing a single requestor session. PAL works on existing data; it does not degrade processing.

Database Trace

The Database Trace tool is useful to tune the application in case of any database performance issues. Run Database Trace if PAL readings indicate performance issues in the database operations. Database Trace can trace all the SQL operations like queries or commits that are performed.

Performance Profiler

Use the Profiler to obtain a detailed trace of performance information about the execution of activities, when condition rules, and data transforms executed by your requestor session. The Profiler traces every execution (in all Threads) of rules of these three types in all rulesets. The Performance Profiler should be run in conjunction with Performance Analyzer to narrow down the specific step (Performance Profiler) of the cause (Performance Analyzer).

For more information about the System Performance landing page, see the help topic System Performance.

This Topic is available in the following Module:

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice