Performance Tunned Trace/ Analysis tool

[Former Member]

Hi,

I am seraching for any tool / utility provided by SAP in the ABAP Development workbench to trace/analyse the perofrmace of DB Accesses , Internal table operations in programs so I could analyse the inefficient ABAP code and could replace the same with efficient.

thanks and regards,

Avakash.

[Former Member]

Hi,

you searched for ST05. This transaction traces SQL and Internal table accesses. For an overview I would recommend SE30.

Best regards

Ralph Ganszky

[Former Member]

Hi,

Goto 'ST05'. Put <b>'Trace On'</b> then run your query in another session. Then Put <b>'Trace Off'</b>. Finally put <b>'Display Trace'</b>. It will show you all Database Fetches within the time period the SQL Trace was on. You can click on <b>'REOPEN'</b> & see the position of the SQL statement in Program & click on <b>Table name</b> & see all the Indices available for that Table. Also you can see parameters on <b>'WHERE' clause</b>..

By seeing the time taken for the Query & the Table Name you can Anlyses the <b>where clause of the Query</b> & either <b>modify your Select Query</b> or <b>Create Index</b> for the required fields of that table.

Reward Points if Helpful.

[Former Member]

there are three tool which we can use to check the performance of the program

1) Run time analysis

2) ST05-Performance analysis

3) Extended code check

1) Runtime analysis. this is available thru the initial screen of se38 and this can be used to check the time taken by different parts of your program.

2) ST05 can be used to check the program against the standard performance criteria.

3) EPC not exactly for performance enhancement but can be used to find some simple errors like improper select single

[Former Member]

Hi Avakash,

Check this info.

You can use ST05 to find the performance of each select.

u can use SE30 - runtime analysis to find which part of your code is taking more time.

using ST05:

activate the trace --> execute the program --> deactivate the trace --> display trace.

then go to Trace list --> Summarize trace by SQL statements.

here u can analyze performance of all the selects.

If you want to compare the duration by the selects in your program itself then use: GET RUNTIME statement.

Hope this resolves your query.

Reward all the helpful answers.

Regards

[Former Member]

Hi,

Most of all the answer you get it to use ST05 and SE30. Apart from that you can go for ABAP Program Extended check using SLIN, so you will get a better idea where to improve.

If helpful than dont forget to give the point and close the thread.

Hitz

[alison_lloyd]

in st05 I always find it more useful to combine table accesses then agregate and then when the problem is clearly identified drill down to look at the specifics.

Be very careful creating a secondary index - this should be considered as a last resort depanding on the table - only generally consider if the program is run regularly in production and the trade off with the entry of data to the table taking longer is acceptable