Workload Overview

Definition
The workload overview outputs data about the workload that is written by the SAP kernel and
displayed using the workload monitor (transaction ST03N). The workload overview provides
system administrators with various detailed information about the most important workload data,
such as CPU time, the number of database changes, response times, and so on.

In SAP Basis 4.6C, the workload monitor was extended so that it now
also includes GUI times, Frontend network times and the RFC time.

Structure
You can display the workload overview for all task types (Dialog, Background, RFC, ALE and
Update) or for one particular task type. The system displays the following data:

Information Explanation Resolution

Average Average time that a workprocess uses ABAP program are expansive due to
CPU Time the CPU; during a dialog step, the CPU improper coding, indefinite, loops,
of the application server is used for multiple conditions.
processing (loading, generating,
processing database requests, ABAP Execute SE30 to debug the program.
processing, and so on).
Should not exceed
The CPU time is determined by the
operating system. At the end of a 40%(response time – wait time)
transaction step, the SAP work process
queries the CPU time from the
operating system. The CPU time is It is not part of the response time
therefore not an additive component of
the response time, unlike wait time, roll
in time, load time and database time.

Average Average time between the time at which Average response time= 600m/s
Response a dialog process sends a request to a
Time dispatcher work process, and the time In the current ECC6 systems Sap allows
at which the dialog is completed and the until 1000m/s
data is transferred to the presentation
layer.

The response time does not include the

time for transferring the data from the
SAP frontend to the application server.
For networks with bad performance, a
 more subjective response time can
therefore emerge. The transfer time is
included in the GUI time and the
Frontend network time.
Average The average time an unprocessed
Wait Time dialog step waits in the dispatcher
queue for a free work process.
Under normal circumstances, the
dispatcher work process should pass a
dialog step immediately after receiving
the request from the dialog step. In this
situation, the average wait time should
be only a few milliseconds. If the
application server of the entire system
is under a heavy load, this can lead to
traffic jams in the dispatcher wait
queue.
Average Average time required to load and
Load and generate objects such as ABAP source
Generation code and screen information from the
Time database.
DB Time Number of logical ABAP accesses to
data in the database; these accesses
are made through the SAP database
interface and are parsed into individual
database calls.
The ratio of database calls to database
accesses is important. If the access to
information in a table is buffered in the
SAP buffer, no database calls to the
database server are required. The ratio
of Calls/Accesses therefore gives an
indication about the efficiency of the
table buffering. A good ratio would be
1:10.
GUI Time Response time between the dispatcher
and the Gui during the roundtrips
(roundtrips are communication steps
between the SAP system and the
frontend during a transaction step).
It should less than 50 m/s or 10% of
response time.
Check the bottleneck if it is temporary, if
not:-
i)increase the work process
ii)there may be expansive programs that
are not releasing the work process,
advice the user schedule them in
background during off-peak hours.
It should not be more then 200 m/s
Check the size of the buffer & buffer
swaps and requested content. If required
enlarge the buffer size.
Should not exceed
40%(response time – wait time), if it
exceeds expansive sql statements such
as
i)select * without using any conditions
ii)Resourse bottleneck on the database
iii)DB buffer size is oo small
iv)DB statistics is not up to date
Run trace in ST01/ST05 and calculate
the cost of SQL statement.
Should not be more then 200m/s
I)Network/DESKTOP issues
Check the bandwidth, Patch the GUI,
upgrade the desktop
 ii)GUI issues

Roll Ins Number of rolled in user contexts

Roll Outs Number of rolled-out user contexts

Roll In Time Processing time for the rolling in of user

contexts

Roll Out Processing time for the rolling out of

Time user contexts

Roll Wait Wait time in the roll area

Time
When synchronous RFCs are called,
the work process performs a roll out
and waits for the end of the RFC in the
roll area. The RFC server programs can
wait for other RFCs to be sent to them
in the roll area.

Enqueue Time take by the Dialog process to 1-5 m/s

time obtain lock from Enqueue process.

RFC . Time taken by the RFC to

time/CPIC communicate with the external systems.
time It should be as minimal as possible

Background information

The response time is usually split into wait time plus execution time. The
SAP response time is made up of the following components:

Response Time = Wait Time + Execution Time

where: Execution Time =

Generation time during the run

+ Load time for programs, screens and the graphical interface

+ Roll times for rolling in the work data
+ ABAP processing time
+ Database time
+ Enqueue time for logical SAP lock processes
 + CPIC/RFC time
+ Roll wait time (excluding Task types RFC/CPIC/ALE)

The CPU time is not an additive component of the response time, but the
total of the individual components of the utilized CPU time. The CPU time
is therefore an additional, independent piece of information about the
response time.