SAP ABAP Performance Check : Quick Reference

SAP System Performance depends upon wide varieties of parameters and system components. There are multiple key T-Codes which can be used for SAP performance check and tuning like ST03N, STAD, ST02, ST06 and so on, but here we will focus on quick reference for the performance check of SAP system.

When user execute any transaction in SAP, it undergoes multiple checks and performs steps. Quick overview is as follows.

Fig. 1 SAP Transaction Steps

Response time from SAP transaction mainly depends on its activity execution across Presentation Layer, Application layer and Database layer. Quick reference of response time and its components is as follows.

Fig. 2 Transaction Response Time & It’s Components

Good response time for a transaction depends upon the response time of the each component involved. Below table shows guideline Values for across components.

TimeGuided ValueProblem Indicated
Dispatcher Wait Time
(Avg. Wait Time)
< 10% of response time
< 50 ms
General performance problem with many causes
Load Time
(Avg. Load & Gen. time)
< 50 msProgram buffer too small or CPU bottleneck
Roll-in time, Roll-out time
(Avg. roll-in time, Avg. roll-out time)
< 20 msSAP roll buffer or Extended memory too small or CPU Bottleneck
Roll-wait time
(Avg. roll-wait time)
< 200 msProblem with front end communication or with external component communication
GUI Time
(Avg. GUI Time)
< 200 msProblem with front end communication
Enqueue Time
(Avg. Lock time)
< 5 msProblem with enqueue, network problem
Processing Time, CPU TimeqProcessing Time < 2 x CPU TimeCPU Bottleneck
Database Time
(Avg. DB Time)
< 40 % Total Response Time minus dispatcher wait time
200-600 ms
Database problem, CPU Bottleneck
Direct Read< 2 msDatabase Problem
Sequential Read< 10 msDatabase Problem
Logical Changes< 25 msDatabase Problem

For workload monitoring, ST03N transaction to be used which provide multiple options to check the activities happening in system during specific time. We have option to check activities by Day, Week or Month. Also checks can be performed for specific duration via “Last Minute Load” option.

Based on the data available, further checks can be planned as below.

Fig. 3 ST03N Checks 1
Fig. 4 ST03N Checks 2

Details about SAP Work Processes can be checked via SM50/SM66.

Fig. 5 SM50/SM66

Details about application Server CPU, Memory, Disk, I/O etc. can be checked via ST06.

Fig. 6 ST06 Checks 1
Fig. 7 ST06 Checks 2

Another major area for performance check is SAP Memory, which can be checked via transaction ST02. SAP Memory consist of three main areas

  • Roll Memory
  • Extended Memory
  • Heap Memory
Fig. 8 SAP Memory areas & Parameters

The way memory used by dialog work process and background work process is different in UNIX environment. Flow is as follows.

Dialog Work ProcessBackground Work Process
Local SAP Roll Memory up-to ztta/roll_firstLocal SAP Roll Memory up-to ztta/roll_first
SAP Extended Memory, until ztta/roll_extension is reached or extended memory is used upSAP Heap memory until abap/heap_area_nondia is reached or SAP heap memory is used up
Local SAP roll memory up-to ztta/roll_area
SAP Heap memory until abap/heap_area_dia is reached or SAP heap memory is used upSAP Extended Memory, until ztta/roll_extension is reached or extended memory is used up
Program TerminationProgram Termination

SAP Database related checks can be performed via transaction DBACOCKPIT or ST04 or DB02, each of them provide access to approx. same information via different tabs.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Powered by WordPress.com.

Up ↑

%d bloggers like this: