Overview of Functions 

Use

The runtime analysis tool allows you to examine the performance of any ABAP programs, such as reports, subroutines, function modules or classes, that you create in the ABAP Workbench. It saves its results in performance data files, which you can display as lists. You can use these results to identify runtime-intensive statements, to combine table accesses, and show the hierarchy of program calls. From the results of the runtime analysis, you can identify:

·        Excessive or unnecessary use of modularization units

·        CPU-intensive program functions

·        User-specific functions that could be replaced with ABAP statements

·        Inefficient or redundant database access.

If you only want to analyze or fine-tune a program’s database accesses, use the Performance Trace. For fine-tuning at system level, use the System Trace function.

 

Measuring the Runtime of Program Segments

Use the runtime analysis tool to measure the runtime of complex program segments or complete transactions.  

If you want to measure the runtime of smaller program segments or individual ABAP statements, use the ABAP statement GET RUN TIME FIELD.

 

Starting the Runtime Analysis

You can start the runtime analysis as follows:

 

Starting from	Choose
Any screen	System ® Utilities ® Runtime Analysis ® Execute
The initial screen of the ABAP  Workbench	Test ® Runtime Analysis
The initial screen of the ABAP  Editor	Program ® Execute ® Runtime Analysis
The ABAP Editor	Utilities ® More Utilities ® Runtime Analysis

 

With larger applications, it is advisable to first analyze the entire application and then search for time-critical calls in the hit lists. You can then examine these systematically by making the appropriate selections in Measurement Restrictions.

 

Restrictions Through Aggregation

Depending on the size of the program, considerable volumes of data can be generated during the runtime analysis. Therefore, this tool is defaulted to full aggregation. As a result, only the standard hit list is generated with all calls. The following information, however, is not generated:

·        Group hit list

·        Hit list of database tables

·        Class hit list

·        Instance hit list

·        Method hit list

·        Event hit list

·        Hit list of internal tables

·        Call hierarchy

·        Statistics

To cancel this restriction, switch off aggregation by replacing the standard variant in the initial screen with a temporary variant, for example. In this variant, you can then configure the measurement restrictions according to the selected objects to be measured.