Skip to main content

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

Profiling all processing on a node

Updated on May 11, 2022

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.

Caution: 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.
Result: The system produces extensive output, saved in files in the temporary files directory.

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