Viewing Component Trace Information

Access the Component Trace page (PeopleTools, Performance Monitor, Analytics, Component Trace).

To view the Component Trace page, a user must have completed a performance trace. This page enables you to isolate the component performance information within a particular performance trace. The information presented appliesonly to component processing.

Note: To gain the most performance data and a clearer insight into component activity, you should run the performance trace that is generating the trace information in debug or verbose mode.

Field or Control	Definition
Performance Trace Name	Displays the name of the trace, which is typically the end user's user ID, but can be whatever name was entered by the end user in the Performance Trace Name edit box on the Performance Trace Console.
Monitor Start Date and Time	Displays the date and time that the monitor began receiving performance information for a particular performance trace.
First Component	Identifies the first component that is accessed during the performance trace.
Component Cache Status	Enables you to determine whether the objects that are associated with a component were accessed from the application server cache or retrieved from the database during the performance trace.
Server Round Trips	Displays the number of server round trips that are related to component processing that were completed during a particular performance trace.
SQL Executes	Displays the number of SQL programs that were run during component processing.
SQL Fetches	Displays the number of SQL fetches that were run during component processing.
PeopleCode Program Executions	Displays the number of PeopleCode programs that were run during component processing.
Email XML File	Enables you to email the data from the Component Trace page in an XML format so that you can share the information with colleagues or PeopleSoft consultants.

Warnings

The Warnings section contains any warnings that may alert you to situations in the trace that may cause discrepancies in or misunderstandings of the trace results. For example, if particular component objects were not fully cached at the time of the trace, a warning appears notifying you of this. Production systems usually cache all frequently accessed objects for better performance. Objects that are not cached can skew results because after an object is fully cached, performance when accessing that object typically increases dramatically. The Description column provides details of the warning and provides considerations or remedies where appropriate.

A warning message appears if the performance trace is not run in debug mode.

Duration Summary

You see a duration summary if the user ran the performance trace with standard or higher filter level.

The Duration section contains information regarding the duration of the entire performance trace as well as other elements of the performance trace, such as the time spent processing SQL and the time spent processing PeopleCode. For example, the duration information may show that the time for the total trace was 50 seconds, and 22 seconds were spent processing SQL while 15 seconds were spent processing PeopleCode.

Note: The duration total is not a sum of the measurements appearing here. The PeopleSoft system does not instrument every aspect of the runtime, and these areas that are not instrumented account for the difference between the total duration and the total of the measurements that are displayed here.

Field or Control	Definition
Measurement	Displays the measurement appearing in the row, such as SQL, PeopleCode, or Total Trace.
Duration	Displays the total time that was consumed by each element of a performance trace. For example, it may show the total trace consuming 50 seconds and 22 seconds were attributed to SQL.
% of Total	Displays the percentage of the total trace value that each element of the trace consumed. For example, if the total trace value is 50 seconds and the SQL value is 22 seconds, the % of total value is 44.

Server Round Trips

The Server Round Trip section contains information for each server round trip that was completed during a particular performance trace. It contains two tabs: Durations and PeopleTools State Management.

You see a duration summary if the user ran the performance trace with standard or higher agent filter level.

The Durations tab contains the following information:

Field or Control	Definition
Seq (Sequence)	Displays the sequential order in which the server round trips were run, with 1 indicating the first round trip of the performance trace.
Action	Displays the action that was completed during the server round trip, such as Load Page/Search Page, Load Search Result, Click PeopleCode Command Button for field FUNCLIB <table.field>. This column is a hyperlink that launches the Round Trip Details page.
Component	Displays the component from which the user invoked the action.
Page	Displays the page within the component from which the user invoked the action.
Duration	Displays the amount of time that each action, or server round trip, consumed.
% of Total Trace	Displays the percentage of the total performance trace duration that each server round trip consumed. For example, if the total trace value is 50 seconds and a particular action consumes 3.5 seconds, the % of total trace is 7.

The PeopleTools State Management tab contains the following additional information:

Field or Control	Definition
Pack/Unpack Time	Reflects the time that was required for serialization (pack) and deserialization (unpack). The value is derived as follows: PMU 427 + 428 duration - (time spent performing SQL in 427 and 428) The value reflects the serialization duration plus the deserialization duration minus any time spent performing SQL as part of serialization and deserialization.
Component Buffer Size	The component buffer size, metric 1, in PMU 401 (ICPanel). The component buffer has to be deserialized by the application server when it is received from the web server, and then serialized when it is sent back to the web server. The larger the buffer, the greater is the impact of serialization overhead on the monitored system.
PeopleCode Global Size	This is the size of the memory that is used for PeopleCode global variables, which are sent to and from the application server during a Jolt request. This is included in the send buffer size and receive buffer size. This is metric 5 for all PMU 412 (Tuxedo Service Summary) rows.

Field or Control

Definition

Pack/Unpack Time

Reflects the time that was required for serialization (pack) and deserialization (unpack). The value is derived as follows:

PMU 427 + 428 duration - (time spent performing SQL in 427 and 428)

The value reflects the serialization duration plus the deserialization duration minus any time spent performing SQL as part of serialization and deserialization.

Component Buffer Size

The component buffer size, metric 1, in PMU 401 (ICPanel). The component buffer has to be deserialized by the application server when it is received from the web server, and then serialized when it is sent back to the web server.

The larger the buffer, the greater is the impact of serialization overhead on the monitored system.

PeopleCode Global Size

This is the size of the memory that is used for PeopleCode global variables, which are sent to and from the application server during a Jolt request. This is included in the send buffer size and receive buffer size.

This is metric 5 for all PMU 412 (Tuxedo Service Summary) rows.

SQL Summary

The SQL Summary section contains additional details regarding the SQL activity during component processing. It contains two tabs: SQL Executes and SQL Fetches.

You see a SQL summary if the user ran the performance trace with verbose or higher agent filter level.

The SQL Executes tab contains the following information:

Field or Control	Definition
Seq (Sequence)	The system orders the rows by total duration. The sequence in this case is a ranking of total duration.
SQL Operation and Tables	Displays the SQL operation and tables (such as UPDATE PS_QUERY_RUN_QRYVW).
SQL Type	Reflects the type of source code making the SQL call. The SQL types are: PeopleTools (PMU 408). Inline PeopleCode (PMU 406). PeopleCode Built-In (PMU 407).
Execution Count	Displays the number of times that the SQL was run during the performance trace.
Total Duration	The total time required by all executions.
Total Duration Average	The average execution duration, as in Total Duration / Execution Count.

The SQL Fetches tab contains the following additional information for each SQL statement that was run:

Field or Control	Definition
Fetch Count	The total count of all SQL fetches that were run during component processing within a particular performance trace.
Fetch Count Average	The average number of fetches per SQL Execute.
Fetch Duration	The sum total of all durations for SQL fetches.
Fetch Duration Average	The system average for SQL fetch durations during component processing.

PeopleCode Summary

The PeopleCode Summary section contains additional details regarding the PeopleCode activity during component processing. These values relate to PMU 404 (PeopleCode Program Execution).

You see a PeopleCode summary only if the user ran the performance trace in debug mode.

The following metrics apply only to the performance information that was collected during the performance trace.

Field or Control	Definition
Seq (Sequence)	The system orders the rows by .
PeopleCode Program	Displays the name of the PeopleCode program that was run.
Execution Count	Displays the number of times this program has been run.
Duration Total	Displays the sum of all durations of the PeopleCode program.
Duration Average	Displays the average duration of the PeopleCode program.
Duration Maximum	Displays the longest duration of this PeopleCode program.
Duration Minimum	Displays the shortest duration of this PeopleCode program.

Round Trip Details

The Round Trip Details page contains a subset of the performance data that appears on the Component Trace page. It enables you to drill down into a specific round trip to gather duration, SQL, and PeopleCode information. The data that is presented in the page is similar to the data in the Performance Trace page. The PMU Details link accesses the completed PMU page with all PMUs that were captured in this action.