STAD

To document any performance observations in a system STAD is an important

tool. Statistical records are the entry point for the performance analysis. It
provides a very good overview where the time in the dialog step was spent
(database time, CPU time which is mainly ABAP processing, GUI
communication, etc.). If deeper performance analysis (tracing) is necessary, it is
clear in which direction it has to go.

Its a technical logging feature implemented in the SAP kernel, and completely
independent of the applications. Each dialog step is recorded; information like
user and program name, response time, CPU time and more is logged. This
information is very useful when you want to analyze the performance (or a
performance bottleneck) of your SAP system. From the statistical records you
can get a hint where you should continue with a detailed analysis: CPU or
database performance, memory issues, analysis of a particular application, and
more.

Just specify date, time, and length of the interesting interval and hit the enter key.
If necessary you can narrow your search by specifying values for the filter
parameters:
For each dialog step the several metrics are shown, e.g. response time, CPU
time, and DB time (scroll to the right to see these columns).
If you double-click one line you will see the details of this statistical record. All
metrics are shown. You will have to scroll down a few pages to see all of them.
The following example just shows a small part of it.

The section is titled Analysis of time in work process. The executed program
was SAPWL_ST03N. The dialog step was started at 15:24:24 and ended at
15:24:30. The response time was 6087 ms, while CPU time was 210 ms.

This information helps if you want to analyze the performance of a single dialog
step. You can see why the response time is larger than 6 seconds. CPU
consumption is not an issue here in this example, but DB time is very high. So
this could be the point where an optimization could start.</p>