topic Re: Running performance trace in Application Development and Automation Discussions

Running performance trace

Former Member — Tue, 22 Jan 2008 20:47:42 GMT

Hello All:

I have a Z program with some performance issues and I would like to run performance trace on the program to see where I could optimize it. Could someone please tell me how I should go about this?

Thanks.

Mithun

Edited by: Alvaro Tejada Galindo on Jan 22, 2008 3:53 PM

Re: Running performance trace

Former Member — Tue, 22 Jan 2008 20:55:12 GMT

You can start with transaction ST05.

And see:

[Performance Trace|http://help.sap.com/saphelp_47x200/helpdata/EN/d1/801f7c454211d189710000e8322d00/frameset.htm]

Rob

Edited by: Rob Burbank on Jan 22, 2008 3:58 PM

Re: Running performance trace

Former Member — Tue, 22 Jan 2008 20:56:06 GMT

You can use ST05 SE30 and ST04 transacctions...Best thing is to analyse the Database plan in order to fix access to the data. Sometimes a simple index can boost you program in 50% -;)

Greetings,

Blag.

Re: Running performance trace

Former Member — Tue, 22 Jan 2008 20:59:53 GMT

Thanks everyone for the feedback. Should I run the trace first and then execute Z program? What are the sequence of actions I need to do? Sorry, I am new to ABAP and appreciate your feedback.

Thanks.

Mithun

Re: Running performance trace

former_member195698 — Tue, 22 Jan 2008 21:00:10 GMT

Check the blog on SQL Trace

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

Also check the blog on SE30 (Runtime Analysis)

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

You have to Start the Trace, Run the Program, Stop the Trace and then List Trace.

Regards,

Abhishek Jolly

Edited by: Abhishek Jolly on Jan 22, 2008 10:01 PM

Re: Running performance trace

Former Member — Tue, 22 Jan 2008 21:02:15 GMT

SQL trace(ST05) provides the developer with the ability to analyse database select statements. Simply execute ST05

to turn on SQL trace, then execute the statement/program you want to analyse. Now turn off SQL trace using ST05

and click on list trace to view the details.

You can also perform traces on other items such as authorisation objects.

Authorisation trace analysis 1. Open two sessions

2. Execute transaction ST01 in one of the sessions

3. Select the authorisation checkbox, note the other traces

you can perform (SQL, RFC, Table Buffer etc)

4. Click the 'Trace On' button

5. Within your other session execte the transaction/report

you want to trace or get the user in question to do it

6. Return to the session where you turned the trace on and

click on 'Trace Off' otherwise it will continue to record

all athorisation checks

7. Click on the 'Analysis' button

8. Enter appropriate data into selection screen such as

Username, type of trace records (i.e. Authorization check)

9. Click on the Execute button.

10. Report displaying trace results will now be displayed

http://www.sapdevelopment.co.uk/perform/perform_sqltrace.htm

Some useful transaction related to this are ..

ST01 SAP system trace

ST02 Buffer statistics.

ST03 Workload analysis.

ST04 Database performance analysis.

ST05 SQL trace .

ST06 Operating system monitor ...

From the recorded SQL trace you can deduce:

· Which SQL statements your application carries out

· Which values the system uses for specific database accesses and changes

· How the system translates ABAP OPEN SQL commands (such as

SELECT) into standard SQL commands

· Where your application positions COMMIT statements

· Where your application makes repeated database accesses

· What database accesses or changes occur in the update section of your

application

Look at the below links, you will get the idea

http://help.sap.com/saphelp_erp2005/helpdata/en/d1/801f89454211d189710000e8322d00/content.htm

http://www.sapbrain.com/TOOLS/SQLTRACE/SQL_TRACE.html

Check the following links:

http://www.sapbrainsonline.com/TOOLS/RUNTIMEanalysis/SAP_runtime_analysis.html

http://www.sapbrainsonline.com/TOOLS/SQLTRACE/SQL_TRACE.html

Regards

shashikanth naram

Re: Running performance trace

Former Member — Tue, 22 Jan 2008 21:04:33 GMT

It should all be in the help file (ST05) I posted the link to.

Basically, what I do is open two sessions. In one, strart ST05. In the other your program. If you know where the problem in the program lies, you can execute to that point. Activate the trace when you reach the point in the program you want to check.

Rob

Re: Running performance trace

former_member195698 — Tue, 22 Jan 2008 21:06:44 GMT

You can also try Code Inspector (Tcode SCI ), it will give the SQL statements in your program which are not using Indexes

(These queries might be the potential Performance degrader)

Regard,

Abhishek

Re: Running performance trace

Former Member — Tue, 22 Jan 2008 21:16:45 GMT

Thanks everyone for the feedback. I rewarded full points.

Mithun.