Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Tracking system utilization for a requestor session with Performance Analyzer

Updated on July 8, 2022

Use Performance Analyzer (PAL) to view cumulative system usage statistics for your requestor session and to add a reading to identify incremental resources that your session consumes.

Note: When you use PAL for Customer Service chat interactions, be aware that a single browser session can be served by multiple requestors.


As Pega Platform operates, it collects statistics about the demands made on processing resources, and the server system's response. PAL summarizes and formats these statistics and presents them as HTML pages.

By viewing this data, you can assess possible sources of improved performance (faster response time or higher throughput) through software changes, hardware changes, or rule changes.

Performance data shows the processing demand statistics of your work since you connected, and may help you assess the performance impact of various approaches or configuration choices.

Performance statistics can help you distinguish between performance issues that arise in the Pega Platform server, the PegaRULES database, or external systems called by the workflow. In all cases, the statistics can help you determine how to improve performance.

Starting PAL

To start PAL, click ConfigureSystemPerformancePAL from the Dev Studio header. This tool is also accessible from the Dev Studio footer by clicking Performance.

Technical notes

When two instances of Pega Platform are installed on a single Windows server (for example, one for testing and one for production), performance tool CPU statistics may not be available on the copy that was started second.

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