runtime analysis

[Former Member]

Hi all,

can any body tell me what is runtime analysis, performance analysis, sql trace, performancec tuning. and what is the difference between them and transaction code for each???

thanks

[Former Member · Accepted solution]

Hi,

Tools provided for Performance Analysis:

Following are the different tools provided by SAP for performance analysis of an ABAP object

1.Run time analysis transaction SE30

This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.

2.SQL Trace transaction ST05

The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.

The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on the SPFLI table in our test program is mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.

The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.

To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.

Important links:[http://www.sap-img.com/abap/performance-tuning-for-data-selection-statement.htm]

[learnabap.blogspot.com/2007/05/runtime-analysis]

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d0db4c9-0e01-0010-b68f-9b1...

Thanks And Reward points if useful

give points please

[Former Member]

hi

RUNTIME ANALYSIS:

The runtime analysis provides an overview of the duration and performance of your source code, from individual statements up to complete transactions.

Choose Menu ® Test ® Runtime Analysis or transaction SE30 to start the runtime analysis. In the initial screen, you see the four main functions of this tool, which can be activated by pushing the corresponding button.

· Measurement in dialog status

· Measurement of external session

· Selection of measurement restrictions

· Evaluation of measurement results

With large applications, it is advisable to first analyze the entire application and then check details in the hit lists.

With the following information you can carry out the analysis, display and interpret the results, and use this as a basis for optimizing your programs

SQL TRACE

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.

1. 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.

Activities

Typically, you should use the SQL Trace when you need to check the behavior of a particular application. This is the following scenario:

...

You launch the SQL Trace application.

You activate the SQL Trace.

You run the application that you want to trace.

You deactivate the SQL Trace.

You set filters optionally.

You evaluate the trace.

You can also evaluate a trace that already exists.

The SQL Trace also provides functions for file administration.

SQL Trace is less suitable for detecting general performance issues. Therefore, we do not recommend that you keep it constantly activated, as it consumes additional resources.

Initial Screen

Calling

You can call the initial screen of the test tool using transaction code ST05 or by choosing Test ® Performance Trace in the ABAP Workbench.

[amit_khare]

Refer SAP help -

http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cafe68c11d2b2ab080009b43351/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/17/358df9c9fee2469105731e10756921/frameset.htm

Regards,

Amit