Skip to main content

Performance Profiler tool

The Performance Profiler is a diagnostic tool that helps you identify and resolve performance bottlenecks in your application. This tool helps identify which parts of an application, such as process steps, Data Transforms, or activities, are causing performance issues. By recording detailed performance metrics during your requestor session, the Performance Profiler creates a comprehensive trace of rule execution times and sequences. This direct correlation between user actions and performance results allows you to efficiently diagnose problems and target your optimization efforts.

Vorsicht: The Performance Profiler requires substantial processing overhead. Stop the Performance Profiler as soon as your data collection is complete.

The tool operates in two distinct phases: first, you record performance readings while executing the relevant functionality, and then you analyze these readings to identify performance patterns and anomalies that require attention.

Hinweis: 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. For more information, see Profiling all node activity.

Interpret Performance Profiler results

In the Performance Profiler results table, click the Download icon to save the results in a comma-separated value file format. The results can then be opened by using any spreadsheet program, such as Excel, to review the Performance Profiler readings.

Match the numbers to the following image to learn more about interpreting the results of the Performance Profile:

  1. Sequence: Marks the beginning of each activity step or other row.
  2. Interaction: Sequence number of the interaction, as recorded in the Performance tool. Starts with 1 on the initial display of the login form.
  3. Activity: Handle of the activity, when condition, or data transform.
  4. Caller: Handle of the activity that called the current rule.
  5. Step: Step number. For when condition rules, this value is always W. For data transforms, this value is always M.
  6. Method Name or When Result: For activities, identifies the method in the step. For when condition rules, displays true or false. For data transforms, this value is blank.
  7. Total CPU time: Total CPU time in seconds for this step. If this step contains a Call or Java instruction, the CPU time of called activities is included.
  8. CPU Time Without Children: Total CPU time in seconds for this step, excluding time for called processing. If this step contains a Call or Java instruction, the CPU time of called activities is not included.
  9. Total Wall Time: Elapsed time in seconds to complete this step. Values reflect the impact of other users on this server, waits for database operations and external events, and so on.
  10. Wall Time Without Children: Elapsed time (wall time) in seconds, for this step, exclusive of any called processing. (This value is useful for isolating the performance of Java steps that may perform extensive processing in addition to calling activities.)
Performance profiler

Check your knowledge with the following interaction: 


Dieses Thema ist in den folgenden Modulen verfügbar:

Wenn Probleme mit den Lerninhalten auftreten, lesen Sie bitte die Pega Academy Support FAQs.

Fanden Sie diesen Inhalt hilfreich?

Möchten Sie uns dabei helfen, diesen Inhalt zu verbessern?

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