Recording Performance Data 

Preparation

By default and for performance reasons, the Performance Trace in the R/3 System is normally switched off. When you decide to analyze a report or transaction using the Performance Trace, you must first establish whether you want to analyze the interaction of reports and transactions, their effects on one another, the behavior of one or more individual reports and transactions, or only program sections.

Trace records are written into a Ring file. This means that trace records can be overwritten. When the file is full, recording continues from the beginning. It is therefore a good idea to log essential procedures separately. To avoid data being overwritten, you can also shorten the trace interval or enlarge the ring file.

See also: Configuring the trace File

Essential Information

Before you can record trace records, you must switch on the Performance Trace for an instance of the R/3 System.

Here, you can determine which trace functions (SQL Trace, Enqueue Trace, RFC Trace) you want to switch on, and for which user or users they should be activated.

You can then run the reports or transactions that you want to analyze, before switching the trace off again.

This process generates a trace file, containing all of the trace records, which you can then analyze, either immediately or later on. If you decide to repeat the trace or analyze the results later on, remember that the data in the trace file can be overwritten (see above).

See also

Starting the Trace

Stopping the Trace