Starting the Trace 

Prerequisites

You can only switch on the Performance Trace for a single instance. You should already have decided the scope of your performance analysis.

Procedure

  1. From the ABAP Workbench, choose Test ® Performance Trace.
    The initial screen of the test tool appears. In the lower part of the screen, the status of the Performance Trace is displayed. This tells you whether any of the Performance Traces are switched on, the users for which they are enabled, and the user that switched it on.
  2. On the initial screen, select the trace functions that you want to switch on (SQL Trace, Enqueue Trace, RFC Trace).
  3. If you want to switch on the trace under your user name, choose Trace on.
    If you want to switch on the trace for another user or user group, choose Trace on for user.
    To enter a single user, specify the user name. To enter a user group, specify a search pattern (you can use the normal wildcards). If you want to change the user or user group, switch off the performance trace and then restart it, entering the new users or user group.
  4. Run the program you want to analyze as normal.

You will normally analyze the performance trace file immediately. In this case, it is a good idea to use a separate session to start, stop, and analyze the Performance Trace.

During a Performance Trace interval (the time between switching the Performance Trace on and off), you can change the trace types at any time. The user (or user group) must remain unchanged during this period.

Result

The results of the trace recording are contained in a trace file. If trace records are overwritten during the trace interval, the system displays a message to inform you when you analyze the trace file.

The Performance Trace records all database access, remote calls, or lock activity. The measurement itself can affect the performance of the application server on which the trace is running. You should therefore switch off the trace, as soon as you have finished with it.