topic Re: Performance Analysis in Application Development and Automation Discussions

Performance Analysis

Former Member — Mon, 30 Oct 2006 07:10:07 GMT

Hi All,

We have a requirement to analyse the execution time for a particular program.

1. Does ST05 provide the time only required for database access or it also covers the time for loops and other processing involved in the program.

i.e. whether it reflects time taken for only SELECT Queries or also the time taken for other processing ( say Loops, If conditions etc in the program ).

Any other transaction which would provide the time including network access, database, program logic etc.

I have gone through SE30, ST30 but didnt found them much useful.

Thanks,

Best regards,

Prashant Patil

Re: Performance Analysis

Former Member — Mon, 30 Oct 2006 07:13:33 GMT

hi,

to avoid this don't write any select statement within the loop check it out with

You can use SQLTrace.

Check this link.

Re: Performance Analysis

Former Member — Mon, 30 Oct 2006 07:15:58 GMT

Hi Prashant,

If you just have to find the execution time for a program you can run it as a background job and get the execution time and joblog in transaction SM37.

Feel free to revert

Regs,

Sameer

Re: Performance Analysis

Former Member — Mon, 30 Oct 2006 07:16:05 GMT

SQL queries, RFC etc. - ST05

program logic (loops etc) - SE30

Re: Performance Analysis

Former Member — Mon, 30 Oct 2006 07:19:16 GMT

In addition, you can go to SM50, search PID using the job name or program name.

Once you get the PID, go to ST04 and see at runtime what the program is doing. You need PID to search in ST04.

Re: Performance Analysis

Former Member — Mon, 30 Oct 2006 07:26:28 GMT

Hi Prashanth,

No in ST05 you can only find the time taken for DB hits as the name says SQL Trace.

To find the performance of Loops and other thing try SRTM and SLIN.

Hope this might helped you.

Thanks,

Prashanth

Re: Performance Analysis

Former Member — Mon, 30 Oct 2006 09:06:09 GMT

The right tool for runtime investigations is TA se30. You start your program in se30 und get an detailed list of runtimes for the several program parts. Furthermore you can restrict your investigations in advance to certain program parts (i.e. classes etc.)

ST05 is the right trace for SQl statements.

Regards,

Thomas