Performance

[Former Member]

Hi,

in ABAP program how we can find the lines which taking more time to excute ,

so that be modifying that rows we can increase performance ,

THX

[Former Member]

st05

[Former Member]

Hi Chaaya,

You can use the transaction ST05 and SE30 to find out which portion is taking more time.

Just search SDN there are lots of tips and tricks to improve performance.

Also details on how to use above transaction is there in help.sap.com

Regards,

Atish

[Former Member]

Hi,

check ur select statements and loop ....endloop statements .

most of the times these statement will take much time.

To know how time they have taken, goto SE30 and check in analysis.

Time taken by a select statement ,

GET RUN TIME FIELD T1.

select .....

..........

.........

GET RUN TIME FIELD T2..

T2 = T2 - T1.

IF T2 < TMIN.

TMIN = T2.

write: tmin.

'tmin' is nothing but time taken by select statement to retrieve the data.

Regads,

kk.

[Former Member]

Hi,

In ST05 , Run ->Activate Trace

Then Execute the Program ...

Come to ST05 -> Deactivate Trace.

then Press -> Analyse Trace.

A List will be displayed which shows the exceution time for each statement

check the link:

http://help.sap.com/saphelp_nw04s/helpdata/en/0e/6a2442db42e22ce10000000a1550b0/frameset.htm

/people/siegfried.boes/blog/2007/09/05/the-sql-trace-st05-150-quick-and-easy

Hope it is helpful

Reward Points for sure...

[Former Member]

Tools for Performance Analysis

Run time analysis transaction SE30

SQL Trace transaction ST05

Extended Program Check (SLIN)

Code Inspector ( SCI)

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.

reward if its helpful...tq

[Abap Tips & notes|http://abap4beginner.blogspot.com]

[former_member251078]

Hello,

SE30 and ST05 are very old tools!!!. You can take both of these traces in ST12 transaction. This is a very good tool for taking both the trace and can do analysis.

SE30 and ST12 traces are very helpful for identifying the statement where the time being spent. There are so many intersting features avaiable in this tool, which is not possible through SE30. Refer SAP Note 755977

Regards

Dileep

[Former Member]

> SE30 and ST05 are very old tools!!!.

But they are still state-of-the-art

> You can take both of these traces in ST12 transaction.

The ST12 is a service transaction on top of the SE30 and ST05 with additional functionality, but not available in all systems. However, for a basic performance tuning of your own coding it is not really necessary to use St12.

There it is enough if you use the old tools, and I have prepared a short guideline:

SQL trace:

/people/siegfried.boes/blog/2007/09/05/the-sql-trace-st05-150-quick-and-easy

SE30

/people/siegfried.boes/blog/2007/11/13/the-abap-runtime-trace-se30--quick-and-easy

Siegfried