Run Time Analysis

Run Time Analysis

It is an additional development workbench
tool for analysing performance of all
ABAP/4 program, transaction and Function
modules.

Run Time Analysis . . . Contd.
To start Run Time Analysis, the different
options are
Workbench -> Test -> Run Time Analysis
OR
System -> Utilities -> Run Time Analysis
OR
Transaction Code SE30
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 session
Start the runtime analysis in a parallel session
Display and process performance files



Run Time Analysis . . . Contd.
In the simplest case, you would enter a short
description and a measurement object (transaction,
program, or function module) to run the analysis in the
current session.
In the Measurement restrictions group box, you can
make more specific restrictions for the measurement.
For example, you may want to include only certain
statements or time periods.

Run Time Analysis . . . Contd.
From the initial screen, you can specify whether
the analysis should run in the same session or in a
parallel session using the Enable/Disable button in
the In parallel session group box.
The Performance file group box contains options
for analyzing performance files.

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 file
at OS level
Run Time Analysis . . . Contd.
Performance files:
These files are created at OS level and
many times occupy large memory
space. So make sure to remove files
which are no longer needed.
Run Time Analysis . . . Contd.
Analysing :
When you click on Analyze, it presents
a beautiful bar chart Run Time
analysis Over view screen with the
following components.
ABAP execution time
Data base execution time and
R/3 system execution time
Run Time Analysis . . . Contd.
Data base execution time should be less
than ABAP execution time.
In addition, it also displays
Hit List
Group Hit List
Call Hierarchy and many more things
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 chronological
sequence of a transaction, program, or
function module.
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-resolution
measurement, the maximum measurement interval is shorter.

Run Time Analysis . . . Contd.
Low This option uses a lower resolution.
Consequently measurement errors are more likely.
However, low resolution has a greater maximum
measurement interval.

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.
Run Time Analysis . . . Contd.
From the results of the runtime analysis, you can
identify:
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 with
ABAP statements
Inefficient or redundant database access.

Run time Analysis . . . Contd.
The measurement time is in Micro
seconds.
If you measure the same program or
the transaction several times, the
results can vary. Many factors make it
difficult to reproduce identical results.
Example : Network traffic.
SQL Trace
SQL Trace
Performance trace function for monitoring
and analyzing SQL statements used in
reports and transactions.
It monitors programs and transactions at
Data base level
Using this facility, for every instruction, you
can display which SQL embedded (declare,
open, fetch ) have been executed and
analyse the system performance.
SQL Trace . . . Contd.
To start SQL Trace, the different options are

Workbench -> Test -> SQL Trace
OR
System -> Utilities -> Performance Trace
OR
Transaction Code ST05

SQL Trace . . . Contd.

Click Trace on push button
Quickly go to SE38 and execute the
program to be traced.
Quickly return to SQL Trace initial
screen and click on Trace off push
button.

SQL Trace . . . Contd.

This Switching off is necessary
because, if it is not done, then SQL
trace will Trace each and every program
or transaction executed in that
particular time. It is quite expensive in
terms of memory and time of the
system.
Analysing Trace file

Click on List Trace .

You can see exactly how the system
handles data base request.
Analysing Trace file

Summary :
It will show summary of data base
requests.
Dump analaysis
Analysis of a program error.
A dump analysis provides the
developer with information about the
cause of a program error and suggests
possible solutions.
Transaction code is ST22.