10-05-2007 12:50 PM
Hi,
can you specifty TCODES under Performance Analysis.Kindlyhelp out.
Regards,
sasi.
10-05-2007 12:53 PM
Hi Sekar,
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.
Some times you will have to use a combination of SE30 and ST05.
I would like to use St05 personally.
SQL Trace (ST05) we use for performance tuning
In se38,you have a report and you want to test the performance of that report
ST05 tells about the summary of sql statements used in that program.
-Go to Tcode ST05
-Select Trace on
-In se38,Execute your report-
-Come back to st05 and select Trace off
-Select Trace list.
Now you check your select stmnts and how much time taking
-Some columns showing pink color are expensive select stmnts
You have so many options inside to check for summary and also index..
http://help.sap.com/saphelp_47x200/helpdata/en/f2/31adaa810c11d288ec0000e8200722/frameset.htm
ST02 --> Memory management
ST03 --> Dialog Service
OS06 --> Operating System
SCI --> Code Inspector
Thanks,
Reward If Helpful.
10-05-2007 12:54 PM
10-05-2007 12:56 PM
Hi Sekar,
Use Tcode
SLIN : extended program check.
SE30 : Run time analysis.
SCID : Code Inspector
Reward points if helpful.
Regards,
Hemant
10-05-2007 1:05 PM
10-09-2007 5:34 PM
Did any one know about se30 output details.I mean in the analyse regarding execution time details.
10-09-2007 6:35 PM
Yes, it is used for doing Runtime Analysis. This runtime analysis tools allows the ABAP programmer to trace the tables used by the SAP dialog/reports programs.
Check this link for more details -
http://www.sapbrainsonline.com/TOOLS/RUNTIMEanalysis/SAP_runtime_analysis.html
ashish
Message was edited by:
Ashish Gundawar