ks-21 abap tools

8/11/2019 KS-21 Abap Tools

1/24

Run Time Analysis


2/24

Run Time Analysis

It is an additional development workbench

tool for analysing performance of allABAP/4 program, transaction and Function

modules.


3/24

Run Time Analysis . . . Contd.To start Run Time Analysis, the differentoptions are

Workbench -> Test -> Run Time AnalysisOR

System -> Utilities -> Run Time Analysis

OR Transaction Code SE30


4/24

Run Time Analysis . . . Contd.

From the initial screen, you can start the following main

functions:Tips & Tricks

Setting the measurement restrictions

Start the runtime analysis in the current sessionStart the runtime analysis in a parallel session

Display and process performance files


5/24


In the simplest case, you would enter a short

description and a measurement object (transaction,program, or function module) to run the analysis in thecurrent session.

In the Measurement restrictionsgroup box, you can

make more specific restrictions for the measurement.For example, you may want to include only certainstatements or time periods.


6/24


From the initial screen, you can specify whether

the analysis should run in the same session or in aparallel session using the Enable/Disablebutton inthe In parallel sessiongroup box.

The Performance filegroup box contains optionsfor analyzing performance files.


7/24

Run Time Analysis . . . Contd. Enter the name of the program ( to be

analysed ) and then click on push

button

Execute

The system will execute the object and

generates Trace file or Performance fileat OS level


8/24

Run Time Analysis . . . Contd.Performance files:

These files are created at OS level andmany times occupy large memoryspace. So make sure to remove fileswhich are no longer needed.


9/24

Run Time Analysis . . . Contd.Analysing :

When you click on Analyze, it presents

a beautiful bar chart Run Timeanalysis Over view screen with thefollowing components.ABAP execution time

Data base execution time and

R/3 system execution time


10/24

Run Time Analysis . . . Contd.Data base execution time should be lessthan ABAP execution time.

In addition, it also displays

Hit List

Group Hit List

Call Hierarchy and many more things


11/24

Run Time Analysis . . . Contd. Hit List : Displays the runtime for each

statement. The list is displayed in descending

order of gross time. Group Hit List : Displays the grouping of the

measurement results.

Call Hierarchy : Displays the chronologicalsequence of a transaction, program, or

function module.


12/24

Run Time Analysis . . . Contd.Record times:

You can choose between two degrees of accuracy for the

measurement:High This accuracy level uses a platform-specific high-

resolution clock. This resides in a special part of the host.

This option reduces the probability of measurement results

being incorrect. However, if you use high-resolutionmeasurement, the maximum measurement interval is shorter.


13/24


Low This option uses a lower resolution.

Consequently measurement errors are more likely.

However, low resolution has a greater maximum

measurement interval.


14/24

Run Time Analysis . . . Contd.The runtime analysis consists of two parts:

Recording performance data

Analyzing the performance data

In the first part, the system measures the transaction,

program, or procedure, and writes the result to a

performance data file..

In the second part, the performance data is analyzed,

and the system displays the results in list form.


15/24

Run Time Analysis . . . Contd.From the results of the runtime analysis, you canidentify:

Excessive or unnecessary use of modularization units(subroutines or function modules) and ABAP statements

CPU-intensive program functions

User-specific functions that could be replaced withABAP statements

Inefficient or redundant database access.


16/24

Run time Analysis . . . Contd.The measurement time is in Microseconds.

If you measure the same program orthe transaction several times, theresults can vary. Many factors make it

difficult to reproduce identical results.Example : Network traffic.


17/24

SQL Trace


18/24

SQL Trace

Performance trace function for monitoring

and analyzing SQL statements used in

reports and transactions.

It monitors programs and transactions atData base level

Using this facility, for every instruction, you

can display which SQL embedded (declare,open, fetch ) have been executed andanalyse the system performance.


19/24

SQL Trace . . . Contd.To start SQL Trace, the different options are

Workbench -> Test -> SQL Trace

OR

System -> Utilities -> Performance Trace

OR Transaction Code ST05


20/24

SQL Trace . . . Contd.

Click Trace on push button

Quickly go to SE38 and execute theprogram to be traced.

Quickly return to SQL Trace initialscreen and click on Trace off pushbutton.


21/24

SQL Trace . . . Contd.

This Switching off is necessary

because, if it is not done, then SQLtrace will Trace each and every programor transaction executed in that

particular time. It is quite expensive interms of memory and time of thesystem.


22/24

Analysing Trace file

Click on List Trace .

You can see exactly how the systemhandles data base request.


23/24

Analysing Trace file

Summary :

It will show summary of data baserequests.


24/24

Dump analaysis Analysis of a program error.

A dump analysis provides thedeveloper with information about thecause of a program error and suggestspossible solutions.

Transaction code is ST22.

ks-21 abap tools

Documents