Performance Analysis

You can use Performance Tracking (transaction code /AIF/PERFORMANCE) to measure the performance of the SAP Application Interface Framework. Using this performance analysis tool, you are able to detect time-consuming routines and processes within the SAP Application Interface Framework.

Using tracking variants available in this transaction, you can track the performance of specific objects, for example, particular interfaces, users, and time ranges within the SAP Application Interface Framework.

Goals

The goals of the performance optimization process and the Performance Tracking transaction include:

Measuring interface performance in back end systems
Determining the area for performance improvements (for example, interface-specific logic and mapping logic)
Defining measures for bottlenecks with most saving potential
Implementing performance improvement measures
Confirming the positive impact of performance improvement measures

Features

Scope

The scope of the interface performance measuring is defined for all interfaces via SAP NetWeaver Process Integration and the SAP Application Interface Framework.

The following are measured:

ABAP Proxy
Interface-specific logic (for example, value mappings and validations)
Posting logic (for example, BAPIs)

The following are not measured:

Legacy extractors
Transmission of data (for example, file transfer and MQSeries)
SAP NetWeaver Process Integration

Activities

You can access the Performance Tracking report from the SAP Easy Access menu by choosing Start of the navigation path Cross-Application Components Next navigation step SAP Application Interface Framework Administration Tools Performance Tracking End of the navigation path .

Set Up Tracking

In order to track performance, a variant needs to be set up. You can either select a variant that already exists or create a new variant. If you select an existing variant, the corresponding data for the variant is displayed on the screen.

If a variant has not been created, the default values are shown in the selection screen of the transaction and the variant is marked as Unsaved. While creating a variant on the selection screen, you can specify a message ID, namespace, interface name, interface version, and the name of the user starting the message. You can also enter the minimum duration and the time range.

You can start tracking by choosing (Start Tracking). You can stop tracking by choosing (Stop Tracking).

Analyze Results

Performance issues could arise in the following areas:

Interface-specific logic
Posting logic (for example, SAP BAPIs)

Examples of performance issues in above areas and possible solutions for you for these issues are shown in the following table:

Examples of Performance Issues	Possible Solutions
Frequent selection of identical data, for example, function modules that are Customized on an item level	Buffering in hashed internal table
Slow select statements, for example, database index not used	Usage of database index, if available Creation of database index, if feasible Database access via alternative table
Long read access to internal tables	Usage of sorted or hashed tables Usage of field symbols
Long runtime of SAP BAPIs	Check for user exits with poor performance Redesign of interface if BAPI supports multi-post