8/14/2019 ST03N Doc

1/3

ST03N: Workload Monitor [Monitoring]

ST03N: Workload Monitor [Monitoring]

ST03N is used to analyze statistical datafor the ABAP kernel and monitor

the perforance of a system. You can display the total values for all instances, and compare

the performance of particular instances over a period of time.

The workload overview provides system administrators with various detailed information

about the most important workload data, such as the !P" tie, the n#$er of data$asec%anges, theresponse ties, and so on. You can display the workload overview for all task

types (&ialog,Backgro#nd, '(!, A)*, and "pdate), or only for one particular task type.

Workload +,er,ie- :.

http://2.bp.blogspot.com/-A0eFDbuFoHs/UJ-pbPKFpfI/AAAAAAAAABw/SLbCOhC8_sQ/s1600/page+1.jpg

8/14/2019 ST03N Doc

2/3

Processing tie This is equivalent to response time minus the sum of wait time, database

request time, load time, roll time, and enqueue time

/int:> ! of "#$ time

Pro$s:%ardware

!P" tie & work process uses the "#$.

/int:' of response time*

Pro$s+"#$ bottleneck

Sol#tion:n ST0,

-o to &etail Analysis Men#> Top !P", check e!istence of /on0 (e!ternal) pro1rams

by sortin1 by "#$ time. Try to run these e!ternal pro1rams in offline hours.

n ST01,

"heck for any swappin1 happenin1 in all the buffers. f there is hi1h swappin1 for any buffer,

increase the si2e of the buffer.

'esponse tie The time when a dialo1 process sends a request to a dispatcher work

process, and the dialo1 is complete and the data is transferred to the presentation layer. The

response time does not include the time for transferrin1 the data from the 0 front end to

the application server.

/int:3 second (dialo1), 43 second (update)

Wait tie The time when a user request sits in the dispatcher queue. t starts when user

request is entered in the dispatcher queue5 and ends when the request starts bein1 processed.

/int:4 3 of response time

Pro$s:lon1 runnin1 tasks, locked tasks, not enou1h work process

Sol#tion:

n SM20,

6ook for all the confi1ured work processes are in 7aitin1 or 8unnin1 state. f all the wotkprocesses are runnin1 state, then increase the number of 9ialo1 work processes.

http://asknadya.com/sap-basis/sm50-%E2%80%93-process-overview-system-monitoring/http://4.bp.blogspot.com/-wlvftLdhd8Y/UJ-pbt2l2NI/AAAAAAAAAB4/4G56hDLVnBc/s1600/page+2.jpghttp://asknadya.com/sap-basis/sm50-%E2%80%93-process-overview-system-monitoring/

8/14/2019 ST03N Doc

3/3

n SM,

This monitor will help to analyse the total work processes confi1ured in all the servers and

instances.

&B calls /umber of parsed accesses to the database./int:9: calls;requests 1ood ratio is 3+3 < efficiency table bufferin1

&B re#ests4&B Tie The time when a database request is put throu1h to the database

interface = when the database interface has delivered the result.

/int:' of response time

Pro$s:"#$;memory bottleneck on 9: server, e!pensive 06 statement, missin1 inde!es,

small buffer, missin1 statistics

Sol#tion:

n ST05,

&ata$ase $#ffer #ality(6 728), if 4, increase database buffer cache si2e. 'eads4"ser !alls(9 30), if >, the e!pensive 06 statements need to be tune. 0ome of

e!pensive 06s statement problems+

i) incorrect inde! access (0olution < create new inde! or reor1ani2e the inde!)

ii) hi1h table si2e (0olution < archive the old entries)

A,erage load generation The time needed to load and 1enerate ob?ects.

/int:4 3 of response time, 4 @ms

Pro$s:#ro1ram buffer, "$& buffer, screen buffer too small

;"< tie 8esponse time between the dispatcher and the -$ durin1 the roundtrips

(roundtrips are communication steps between the 0 system and the front end durin1 a

transaction step).

/int:4 ms

Pro$s:network between -$ = 0*

Sol#tion:

n ST0,

-o to &etail Analysis Men#> )AN !%eck $y P