Using the summary display of Performance Analyzer
Use 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:
| Link | Effect |
| Add Reading | A 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 Data | Initializes 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 |
| Start DB Trace | Starts the DB Trace tool to trace PegaRULES database operations. |
| DB Trace Options | See Database trace options. |
| Start Profiler | Starts the Profiler to provide detailed CPU statistics for activity steps. When you select the link, it 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 ). |
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.
| Link | Effect |
| Start DB Trace | Starts the DB Trace tool to trace PegaRULES database operations. |
| 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 ). |
| Show Graph | Presents a bar chart highlighting major factors affecting performance. |
| My Alerts | Provides additional detail on alerts from your own requestor session (or other filter criteria you provide). |
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.
| Label | Description |
| full | Statistics 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. |
| init | The 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.
The following table lists and describes the columns on the System Performance landing page.
| Label | Description |
| Int # | Sequence number of the most recent completed interaction. |
| Int Count | Total number of interactions. |
| Total Elapsed | Total elapsed time for this interaction. |
| RA Elapsed | Rules assembly elapsed time. |
| Rule I/O Elapsed | Elapsed 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 Elapsed | Elapsed time accessing non-rule-resolved instances from the PegaRULES database plus elapsed time retrieving non-rule database lists. |
| Total CPU | Total CPU time used. |
| RA CPU | CPU time spent assembling Java classes. |
| Rule CPU | CPU time spent executing rules. |
| Other CPU | CPU time excluding rules assembly CPU and Rule CPU. |
| RA Count | Number of Java classes assembled. |
| Rule Count | Number of times rules are found. |
| Activity Count | Number of activities started by this thread, including activities where an exception occurred during execution. |
| Connect Count | Number 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 Bytes | Total bytes of input and output. |
| Memory Allocated pxBytesAllocated | Approximate memory allocated for the interaction. The value displayed is approximate because some Java virtual machine implementations might use object allocation mechanisms that result in a delay between the time that the system allocates an object and the time that the system records the heap size. Heap space reclamation has no effect on the allocated memory. For more information, see PEGA0133 alert: Allocated memory threshold reached. |
Previous topic System Performance landing page Next topic Using the full details display of Performance Analyzer