Interpreting Performance Profiler results
Interpret the results of Performance Profiler so that you can identify what changes might improve system performance.
- The resulting table lists a Profiler .csv file for each thread that you used, identified by your Requestor ID and Thread Name. Select a .csv file for the thread of interest to you and click the Download this file icon in the Actions column to send the file to your workstation.
- Open the .csv file with Microsoft Excel to review and analyze the data. The
Profiler .csv file includes the following data columns in each row.
Name Description Sequence Marks the beginning of each activity step or other row. Interaction Sequence number of the interaction, as recorded in the Performance tool. Starts with 1 upon initial display of the login form. Activity Handle of the activity, when condition, or data transform. Caller Handle of the activity that called the current rule. Step Step number. (For when condition rules, this value is always W. For data transforms, this value is alwaysM.)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. 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. 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. 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. 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.)
Previous topic Profiling your requestor session Next topic Profiling all processing on a node