The Line Summary view provides detailed performance metrics for each executable line in the profiled module. The view opens automatically when you open a .prof file. You can manually open it by selecting Window > Show View > Other > Profiler > Line Summary from the main menu.

The view has a right section and a left section. The right section displays the debug listing content of the profiled module. This information appears only if you select the Generate Debug Listing files check box in the Profiler tab of Run Configuration. The left section displays line-level performance data for the module, including the following:
Tab Description
Line Number The line number in the module file that was executed.
Times Called The number of times this line was executed during profiling.
Average Time (secs) The average time taken for each execution of this line.
Total Time (secs) The total time spent executing this line across all calls.
Note: The Line Summary view uses compiler-generated debug listings to map profiler data to the correct source snapshot. If listing files are missing or not in the listing directory, the view uses the current source code, which might differ from the profiled code.

PDSOE Profiler expects the debug listings to be in a folder named listing (case-insensitive) inside the profiling output root. If the folder name is different, the Line Summary view shows the current source instead of the profiled snapshot.

To avoid discrepancies, you need to perform any one of the following tasks:

  • Enable Generate Debug Listing files in the Profiler tab of Run Configurations. With this configuration, Developer Studio automatically creates the listing folder in the correct location and puts the listing files in it.
  • Use the PROFILER system handle with the Directory attribute.
    
PROFILER:DIRECTORY = "<profiling output root>"
/* Ensure a subfolder named 'listing' exists under this root for debug listings */

    For example, when you set <profiling output root> as C:\OpenEdgeProjects\MyProfileData, then make sure there is a listing folder inside MyProfileData.

  • Use the -listings startup parameter to generate listings in the correct location.
    -listings "<profiling output root>\listing"

    For example, when you set <profiling output root> as C:\OpenEdgeProjects\MyProfileData, then use -listings "C:\OpenEdgeProjects\MyProfileData\listing"