Tools in Performance Tunning

[Former Member]

What are the tools in performance Tunning in ABAP/4

Thanks Regards,

Kumar

[Former Member]

What are the tools in performance Tunning in ABAP/4

Thanks Regards,

Kumar

[amit_khare]

SLIN,SE30 & ST05.

Check these links too.

<a href="https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abapPerformanceandTuning&">https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abapPerformanceandTuning&</a>

<a href="http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_PerformanceAnalysisTools.asp">http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_PerformanceAnalysisTools.asp</a>

<a href="/people/rob.burbank/blog/2006/11/16/performance--what-will-kill-you-and-what-will-leave-you-with-only-a-flesh-wound:///people/rob.burbank/blog/2006/11/16/performance--what-will-kill-you-and-what-will-leave-you-with-only-a-flesh-wound

<a href="http://www.allsaplinks.com/performanc_tuning.html">http://www.allsaplinks.com/performanc_tuning.html</a>

<a href="http://www.sap-img.com/abap/abap-fine-tuning.htm">http://www.sap-img.com/abap/abap-fine-tuning.htm</a>

Regards,

Amit

Reward all helpful replies.

[Former Member]

SE30 - gives you a run time analysis and points out the issues more at design time.

ST05 - Is the most useful if you want to track time taken for execution of each of the sections.

SM50 - Will give you a work process overview, not sure at a program level how can it help you.

SE30 - to check the data base utility

http://help.sap.com/saphelp_47x200/helpdata/en/f2/31adaa810c11d288ec0000e8200722/frameset.htm

[Former Member]

HI,

<b>Run time analysis transaction SE30</b>

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

<b>SQL Trace transaction ST05</b>

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.

http://www.erpgenie.com/abap/performance.htm

Regards

Sudheer

[Former Member]

Check out these

Run Time Analyser

http://help.sap.com/saphelp_47x200/helpdata/en/c6/617cafe68c11d2b2ab080009b43351/content.htm

SQL trace

http://help.sap.com/saphelp_47x200/helpdata/en/d1/801f7c454211d189710000e8322d00/content.htm

Runtime Monitor

http://help.sap.com/saphelp_47x200/helpdata/en/b5/fa121cc15911d5993d00508b6b8b11/content.htm

Memory Inspector

http://help.sap.com/saphelp_47x200/helpdata/en/a2/e5fc84cc87964cb2c29f584152d74e/content.htm

Regards,

Santosh

[Former Member]

kumar,

This are the transactions used for the performance tuning.

<b>SLIN- Extended syntax check.

SE30 - Run time Analysis.

ST05 - SQL Trace.

ST20 - Dynpro Trace.

AL21 - To analyse the performance of ABAP Program.

SM21 - System log.

ST22 - ABAP Dump Analysis</b>.

Regards...

Arun kumar.

[Former Member]

Hi kumar,

Tools provided for Performance Analysis

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

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.

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.

how to perform sql trace:

Poorly written SQL statements have the greatest impact on application performance. An SQL

statement using which an Oracle database system reads and/or sorts thousands or even millions of

rows of data can bring the database to a standstill. Indexes should be used properly to prevent such

situations from occurring. To analyze such problems you should use the SQL Trace (TCode ST05) to

with database access operations.

CAUTION

Only one person can perform an SQL trace at a time. Remember to turn off the

trace when you are finished. SQL trace slows the system down.

1. Using SQL Trace

1. Open a program that you want to analyze, in the editor, so that it is ready and waiting to be

executed.

2. Open a new session using the menu path System Create session.

3. Run transaction ST05 (enter /nst05-zero-five, not oh-five in the Command field, or choose

the menu path System Utilities Performance Trace).

4. Then the initial screen of the test tool appears.

The status of the Performance Trace is displayed in the lower part of the screen. This status tells you

three things namely

Whether any of the Performance Traces are switched on

The users for whom Performance Trace is enabled

The user that switched the Performance Trace on

If the trace is switched on you must switch it off before you can proceed. There are two cases in

which the trace needs to be switched off. They are

If the trace was started within the past hour, it is possible that it is still being used. Contact the

indicated user or try again later

If the trace was started hours or days ago, the user probably left it on by mistake and it can be

safely turned off

To turn off the trace, press the Trace Off pushbutton.

5. The initial screen has various trace functions such as SQL Trace, Enqueue Trace, RFC

Trace

6. Select SQL Trace.

7. There are various options under which trace can be switched on. They are

If you want to switch on the trace under your user name, choose Trace on.

If you want to switch on the trace for another user or user group, choose Trace on for user.

To enter a single user, specify the user name.

To enter a user group, specify a search pattern (you can use the normal wildcards).

If you want to change the user or user group, switch off the Performance Trace and then restart it,

entering the new users or user group.

8. Now switch back to the window containing your editor session (the one with your program

waiting to be executed).

9. Press F8 to run your program.

Note Just press F8 and do nothing. Do not even press the Back button.

10. When your program has run and the hourglass is no longer displayed, switch back to the trace

window.

11. Press the Trace Off pushbutton.

12. Once Performance Trace is switched off, you can analyze the data

Using Runtime Analysis Tool (SE30)

1. You can open the Runtime Analysis tool as follows:

To start from Choose

Any screen System Utilities Runtime Analysis Execute

Initial screen of ABAP

Workbench

Test Runtime Analysis

Initial screen of ABAP Editor Program Execute Runtime Analysis

ABAP Editor Utilities More utilities Runtime Analysis

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

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

(For further information refer section 3. 0).

4. To start the measurement, choose Measure runtime. 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.

5. Run the transaction, program, or function module as normal.

6. Return to the initial screen of the Runtime Analysis transaction. To do so, either leave

transaction, program, or function module as normal, or start the runtime analysis again.

7. The name of the performance data file that has just been created is displayed at the bottom of

the initial screen. The file created by the system is added to the list of performance data files.

You can now analyze, print, or delete the file, or save it locally. The Performance file group

box contains options for analyzing performance files. (For further information refer sections 4.

0 and 5. 0)

regards,

keerthi