Skip to main content

Table of Contents

Profiling all processing on a node


Only available versions of this content are shown in the dropdown

You typically use the Performance Profiler to profile rule usage of one requestor, but you can also profile all activity for a node to get an overall picture of system usage.

Do not enable system-wide profiling on a production system, as doing so may significantly impact performance. On a development system, remove or disable this setting as soon as the you capture the needed processing details.

To profile all processing on an entire server node, do either of the following steps.

  1. Update the prconfig.xml file and restart the server.

    1. Update the prconfig.xml file to add the setting: <env name="Initialization/ProfileApplication" value="true"/ >.

    2. Stop and restart the server to implement the new setting.

  2. As an alternative to updating the prconfig.xml file, you can use dynamic system settings to configure your application. See Configuring dynamic system settings.

The system produces extensive output, saved in files in the temporary files directory.
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega Community 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
Contact us