FAQ: Performance Trace
Q1: What is the transaction name for the SAP NetWeaver Performance Trace?
The transaction name is /IWFND/TRACES.
Q2: How many days remains a trace in system?
Once written a trace expires after two days and is deleted by a cleanup batch job of SAP NetWeaver Gateway. You can mark some trace entries and change the expiry dates to suit your own requirements.
Q3: Will a trace be written even if the OData request is terminated with error?
Once the OData request is passed to the SAP NetWeaver Gateway framework (after a successful login) a trace is written and contains only entries and times up to the location of the error. Therefore, you can also use the trace to check how far your request has been processed within the framework. In this case, you can click Error Log to directly navigate to the Error Log.
Q4: How can I display traces of different OData requests?
You have to mark different trace entries in the trace overview and click Display selected entries.
Q5: What do the duration (ms) and Net Time (ms) mean?
Duration (ms) is the duration in milliseconds of the current call. Net Time (ms) is the real processing time of the current call. The difference between theses times is the processing time of the sub-calls. The sub-calls have a higher level than the current call.
Q6: How can I display the source codes of a call?
You have to mark a trace entry and click Source Code. A new SAPGUI will appear to display the source code located in the SAP NetWeaver Gateway hub system or in the SAP Business Suite backend system. The field Location identifies the system where the current call is processed.
Q7: I can see the RFC and Network overhead in the trace summary. How can I determine this overhead time in the trace details?
Look for entry with “Call Backend - <RFC Destination>”. The net time of this entry is the RFC and Network overhead of an RFC.
Q8: How is the duration computed when Multi-Origin with parallel processing is used?
In the trace summary you see an entry with operation name “Multi-Origin – Parallel”. This entry contains the times of the entry READ_ENTITYSET with the largest sum of RFC and Network Overhead, GW Backend Framework Overhead and Application Time.
Q9: How are the durations computed when $batch parallelization is used with at least SP 08 in both SAP NetWeaver Gateway hub and backend system?
The $batch parallelization for consecutive retrieving operations in backend system is available from SAP NW Gateway 2.0 SP08 onwards. See chapter about Performance Improvement: $batch Paralelization in Some new features in SAP NW Gateway 2.0 SP08 for more details.
In the trace summary you see an entry with operation name “PARALLELIZE_QUERIES”. This entry contains the times of the entry READ_ENTITYSET with the largest sum of RFC and Network Overhead, GW Backend Framework Overhead and Application Time. The SAP NetWeaver Gateway backend framework time in this entry is the sum of the most expensive READ_ENTITYSET and a small time for the internal parallelization overhead.
Q10: Can I replay a request from within a performance trace?
An OData request can be a retrieve or modifying operation with or without request payload (application data) but the performance trace has to be quick and therefore it does not store the request payload. Consequently, a direct replay from within a performance trace is not available.
What you can do, however, is activate the Payload Trace (available from SP 07 onwards) to store all OData requests for which you want to measure the performance. After that, you deactivate the payload trace and activate the performance trace and do different replays from within the payload traces.
Q11: Is the performance trace integrated in Solution Manager?
Yes, the performance trace can also be activated by the HTTP Plugin (SAT Trace flag) and the performance trace summary will be displayed in Solution Manager.
Q12: Can I somehow see the processing times in the gateway framework and provider application without having activated the performance trace?
Yes, this is available from SAP NW Gateway 2.0 SP08 onwards and the so-called Performance Statistics can be required by an OData consumer. See chapter about Performance Statistics in Some new features in SAP NW Gateway 2.0 SP08 for more details.