run time analysis

[Former Member]

hi

what is run time analysis? when will we use that?

[Former Member]

Hi,

this is used to check the performance of ABAP program. Just search SDN ..you will find lots of material on the same,

Regards,

Atish

[Former Member]

Hi,

Runtime Analysis checks program execution time in microseconds. When you go to se30.if you give desired program name in performance file. It will take you to below screen. You can get how much past is your program.

In SM30(Runtime Analysis), Abap, database and System are the three rows which indicate the performance of our program.

These indicate the load on them by the program, which is determined by the length of the bar beside them.

For better performance, abap should be around 90% +, database should be 10% - and system can be around 20% - 45%.

This means that if the load on the database is less , performance is more. For abap the % should be more indicating the fine tuning of the coding so that DB load can be reduced to improve the performance.

Runtime Analysis tells you about the following things(conclusions):

1.How much time is taken for exicution

2.How much Data base access time taken

3.How much Report exigution time taken

4.How much memory is used for the program

etc..

All these information can be had by UTILITIES>MORE UTILITIES>RUNTIME ANALYSIS.Then a dialog box appears,Press Exicute,Go back ,Press analysis.

regards

reena

[Former Member]

hi,

Runtime Analysis:Runtime analysis shows you how long it takes to process ABAP code, from single statements to a complete transaction.

To start the runtime analysis, choose Tools -> ABAP Workbench -> Test -> Runtime analysis (or transaction SE30). On the initial screen you can choose one of four main functions.

Measurement in the current status

Measurement in a new session

Select measurement restrictions

Analyze performance data

For large applications it is recommended that you first analyze the entire application and hit list.

SQL TraceThe SQL Trace function is an on-demand log of selected SQL statements that are issued against the database through the Open SQL Engine. The SQL Trace can be switched on or off dynamically. The log format is database independent. Besides the SQL statement text, each log record contains information about the point in time when the statement was executed, its duration, its input parameters and results (where applicable) as well as context information.

Features

The SQL Trace is especially useful for:

· Development

SQL Trace can help JDO, enterprise beans, servlet and JSP developers to learn which kind of database accesses their code produces.

· Performance analysis

Typically, performance issues are caused by inefficient database accesses. In this case SQL Trace can be used to show the issued SQL statements and their duration, thus helping to identify inefficient SQL statements.

Message was edited by:

Roja Velagapudi

[Former Member]

Hi,

Run time analysis tool captures information about a program as it's being run.after the pgm cmpletes this information, it can be dislplayed for the programmer to get a better understanding of what occured during execution.

like which DB tables are being accessed,how long it took to retrive the information and which subroutines took most time to process.the programmer can then use this information to focus on the parts of the program which most affects the runtime.

This tool is accessed via transaction SE30.

Reward if helpful

Regards

Raghavendra.D.S

[Former Member]

answered

[former_member557670]

Hi vennila,

Runtime analysis used for performance analysis of program or transaction or function module.

use Trcode:se30.

when we go to this transacton we find there r 3 options for analyse,

i.e program ,transaction ,function module.

if we give program name and run the program ,

and come back and choose analyse button,

we get a bar chat ,

in that we get the program execution time,database time and system time in micro seconds.

always abap time is more compare to the system and database time if more preffarable in performance wise.

Reward Points if Answer is useful.

Regrds:

Raju.R

[kiran_k8]

Vennila,

Suppose there are 10 to 12 select statements in your report and some of the tables used are cluster tables and the fields in the where clause of the select statement are neither the primary key nor an index,nor in the same sequence as they are in the table or in the index then, when the program is run in production server it will sleep,I mean it takes lot of time to get executed.

Mind you the same program will work very fine if run in Dev or Quality.The reason is the amount of data in Dev and Quality is less but where as in Production it is live data and will be definitely more.

SE30 will give us a clear picture which is taking more time i.e

ABAP or Database or System time.

ST05 will let you know which of the select statements are taking much time to execute,so that you can fine tune them.

Search for the key words "Optimisation-SQL" in ABAP general,you will get the thread posted by me which answers your question too.

K.Kiran.