Aggregation (SAP Library - ABAP

Aggregation

You can restrict the runtime measurement to particular objects by choosing Change from the Measurement restrictions group box on the initial screen of the runtime analysis.

If you choose Duratn/type, the aggregation type is displayed as well as the size of the performance data file and the time limit for the measurement.

This graphic is explained in the accompanying text

Aggregation reduces the number of entries written in the performance data file because the volume of data generated can be quite considerable particularly with large programs. There are two types of aggregation: full aggregation and aggregation by call.

In full aggregation, all performance data for a particular type of event is summarized in a single performance record.

In aggregation by call, all performance data from a particular event onwards is summarized.

You can use aggregation as the first step in your runtime analysis to identify the most time-consuming calls. You can then restrict your second, more detailed analysis to these objects.

Note Certain information is not available when you use aggregation. If you use full aggregation, only the standard hit list is generated, there is no hierarchy, and you cannot switch to the call. The effect of the display filter is that the events are displayed without their net times being recalculated. If you also want to output memory usage in bytes, aggregation must be deactivated.

Note If you intend to repeat the measurement, you can save your entries as a variant by choosing Save as… If you choose Save ( ENTER ) instead, the existing variant is stored with your changes. If you change the DEFAULT variant, the changes are saved as a temporary variant.