Skip to end of metadata
Go to start of metadata


It's necessary to record a performance trace in order to analyze the time spent in the BWA kernel by bad indexing or query performance, for example. The performance trace with suffix ".tpt" is very important for analyzing the performance issue.

How to record a Perf. trace

There're two ways to record the performance trace. One is from python Admin Tool and the other is from transaction RSDDBIAMON2.

  • Record the Perf. trace from python Admin Tool

         1. Go to python Admin Tool -> Perf. Trace -> Start

             (If you know how long it will take, then you could specify the time to stop. Otherwise you could use "0" to stop manually.)

         2. Reproduce your scenario

         3. To manually stop the trace, go to python Admin Tool -> Perf. Trace -> Stop

         4. Save the trace in python Admin Tool -> Perf. Trace -> Save

  • Record the Perf. trace from transaction RSDDBIAMON2

         1. Go to transaction RSDDBIAMON2 -> Performance Trace -> Start Trace Recording

         2. Specify the user and the time to stop the trace recording, if necessary

         3. Execute "Start Trace Recording"

         4. Reproduce your scenario

         5. Save the trace in RSDDBIAMON2 -> Performance Trace -> Save Trace File

 How to check if a Perf. trace is correctly recorded

1. Go to python Admin Tool -> Perf. Trace -> Load

2. Choose the .tpt file recorded before

3. After loading, go to python Admin Tool -> Perf. Trace -> Calls. Here you can see that different Services/Methods take different Duration/Processing time like following:


4. If you double click one line in step 3, you could see the details under tab Call Pattern:

5. Under python Admin Tool -> Perf. Trace -> Call Patterns, it will show all the Call Patterns details:


If all the Calls and Call Patterns are displayed normally, then this performance trace file is correctly recorded.

For more details, refer to SAP Note 1318293