Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Using the summary display of Performance Analyzer

Updated on April 5, 2022

Use the Performance Analyzer (PAL) to understand the system resources consumed by your requestor session and the SQL statements sent by your session to the PegaRULES database.

Using the links

Use these links at the top of the summary display:

LinkEffect
Add ReadingA new row of summary performance data appears. Statistics include input/output, elapsed time in seconds for certain processing, cache performance, locking, and server CPU demand, for the most recent interaction. Optionally, first click elsewhere in the portal window and perform one or several interactions that cause the performance you want to measure. The system retains extensive data for each interaction.
Add Reading with Clipboard Size A new row of summary performance data appears, including the size of the clipboard in bytes. Similar to Add Reading , but may add potentially costly processing. To learn the size of each page, use the Admin Studio Requestor Management tool to analyze the clipboard. See Managing requestors.
Reset DataInitializes all counts and totals to zero.
Save Data

Lets you save more than 100 statistics and values from each row into a Comma-Separated-Values file (CSV file type) for analysis with Microsoft Excel or other facilities. Column headings correspond to properties in the Code-Pega-PAL class, as presented on the Full Details display. (The value NaN indicates that a statistic was not available.)

Start DB Trace Starts the DB Trace tool to trace PegaRULES database operations.

See Interpreting database trace results.

DB Trace Options See Database trace options.
Start Profiler

Starts the Profiler to provide detailed CPU statistics for activity steps. When you select it, the link changes to Stop Profiler. Execute the activities or other rules to be profiled. Click the Stop Profiler link when you are finished. The resulting window lists a Profiler file for each thread that you used, identified by your requestor ID and thread name. Select a file for the thread of interest to you and click Download or Display Data to send the CSV file to your workstation. Choose Open or Save in the Windows dialog box. Open the file with Microsoft Excel to review and analyze the data.

You can also access this functionality using the Performance Profile tab on the Performance landing page ( Dev Studio > System > Performance ).

See About the Performance Profiler landing page tab.

For each summary row, many more statistics are available on the full detail page. To see full details, click the Full or Init link on a row.

The following choices are available from the Summary display only when you have accessed the summary by clicking the Performance icon in the footer of Dev Studio.

LinkEffect
Start DB Trace Starts the DB Trace tool to trace PegaRULES database operations.

See Interpreting database trace results.

DB Trace Options See Database trace options.
Start Profiler

Starts the Profiler to provide detailed CPU statistics for activity steps. When you select it, the link changes to Stop Profiler . Execute the activities or other rules to be profiled. Click the Stop Profiler link when you are finished. The resulting window lists a Profiler file for each thread that you used, identified by your requestor ID and thread name. Select a file for the thread of interest to you and click Download or Display Data to send the CSV file to your workstation. Choose Open or Save in the Windows dialog box. Open the file with Microsoft Excel to review and analyze the data.

You can also access this functionality using the Performance Profile tab on the Performance landing page ( Dev Studio > System > Performance ).

See About the Performance Profiler landing page tab.

Show Graph Presents a bar chart highlighting major factors affecting performance.

See Interpreting the Performance Summary chart.

My Alerts Provides additional detail on alerts from your own requestor session (or other filter criteria you provide).

See Working with the My Alerts display.

Understanding the basic statistics

The basic statistics display has three or four rows. On the initial display, statistics in the row labeled Full match those in the bottom row.

As you interact with Pega Platform, the statistics change to reflect the results of each interaction.

LabelDescription
fullStatistics in the top row reflect totals since your session started, or since the most recent Reset Data operation.
(none)The second row provides labels for the columns.
delta Delta rows appear as you interact with Pega Platform. Each row shows values from a single interaction.
initThe bottom row shows the totals when this Performance display first appeared.

Columns of the display identify these counts and timings. The table below describes returned data. All CPU time is in milliseconds. The properties are stored in the PALPhase clipboard page, and are in the Code-Pega-PAL class.

The number of decimal places in timing results depends on the hardware and software in use. In general, the decimal values shown are significant. Measurement values are since log-in, or since the last Reset, or incremental between rows, depending on the row label.

LabelDescription
Int #Sequence number of the most recent completed interaction.
Int CountTotal number of interactions.
Total ElapsedTotal elapsed time for this interaction.
RA ElapsedRules assembly elapsed time.
Rule I/O ElapsedElapsed time spent finding rules.
RDB I/O Elapsed

pxRDBIO

Elapsed time executing SQL operations against the PegaRULES database; excludes Connect SQL executions for the PegaRULES database or external databases.
Connect Elapsed

pxConnectElapsed

Time spent waiting for an Connect rule execution to an external system .
Other I/O ElapsedElapsed time accessing non-rule-resolved instances from the PegaRULES database plus elapsed time retrieving non-rule database lists.
Total CPUTotal CPU time used.
RA CPUCPU time spent assembling Java classes.
Rule CPUCPU time spent executing rules.
Other CPUCPU time excluding rules assembly CPU and Rule CPU.
RA CountNumber of Java classes assembled.
Rule CountNumber of times rules are found.
Activity CountNumber of activities started by this thread, including activities where an exception occurred during execution.
Connect CountNumber of connector attempts made to external systems.
Other I/O Count

pxOtherIOCount

Number of times Pega Platform attempts to create lists from the database.
Alert Count

pxAlertCount

Number of alerts created by your requestor session.
Total BytesTotal bytes of input and output.
  • Previous topic Track system utilization for a requestor session with Performance Analyzer
  • Next topic Using the full details display of Performance Analyzer

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us