The dialog response times displayed in the alert monitor (transaction RZ20) and in the workload monitor (transaction ST03/ST03N) are not identical.
1. In kernel releases 6.40 and 7.00 (Releases 6.10, 6.20, 6.40 and 7.00), the dialog response time in the workload monitor consists of the following components:
Dialog response time =
Response time in the application server +
Queue time +
Roll wait time
In the alert monitor, the queue time and the roll wait time were not included in the calculation previously.
2. The system also added data records for RFC server activities in the dialog process at the dialog response time. These data records are not part of the dialog response time as such.
3. The system also added data records for 'AutoTH' and 'Buffer Refresh' to the dialog response time. These, however, are not part of the dialog response time as such.
4. The queue time and the roll-in wait time were added to the dialog response time twice.
1. The problem is corrected with the following kernel patches:
7.00 Kernel: Patch level 38
6.40 kernel: Patch level 106
As of this patch level, the calculation of the dialog response time in the alert monitor is adjusted to the calculation method in the workload monitor.
2. The problem is corrected with the following kernel patches:
7.00 Kernel: Patch level 101
6.40 kernel: Patch level 174
3. The problem is corrected with the following kernel patches:
7.00 Kernel: Patch level 109
6.40 kernel: Patch level 182
4. The problem is corrected with the following kernel patches:
7.10 Kernel: Patch level 90
7.00 Kernel: Patch level 146
6.40 kernel: Patch level 219
The response time of a dialog step is the duration from the request for the dialog to the dispatcher using processing to the completion of the dialog in the dispatcher and the data transfer to the presentation layer.
The response time also includes the time consumed during the roundtrips for the data transfer from the R/3 front end to the application server and back. On the application server, this time is displayed as the roll wait time, whereas it is displayed as the GUI time in the front end. In low performance networks such as WAN connections, this time can add to the response time considerably, although it does not consume any resources on the application server because the context is paged out and the work process is released.
In general, the response time is divided into the wait time and the execution time. The SAP response time consists of the following components:
Response time = wait time + execution time
with: Execution time =
Generation time during runtime +
Load times for programs, screens and graphical user interfaces +
Roll times for the roll-in of the work data +
ABAP processing time +
Database time +
Enqueue time for logical SAP lock processes +
Roll wait time (except for RFC/CPIC/ALE task types)