topic Re: code checking in Application Development and Automation Discussions

code checking

Former Member — Wed, 26 Mar 2008 17:32:31 GMT

Hi experts,,

In real time we will develop programs as per client requirement Ok,

If I want to check the performance of particular program where I have to check

Plz tell me ,

Points Will be rewarded

Thanks ,

Durga Prasad.

Re: code checking

valter_oliveira — Wed, 26 Mar 2008 18:08:36 GMT

Hello.

Use transactions ST05 and SE30.

Best regards.

Valter Oliveira.

Re: code checking

Former Member — Wed, 26 Mar 2008 18:49:58 GMT

Hello Durga,

First use transaction STAD (similar to STAT) or SM50. Here you can roughly evaluate where the bad performance is caused by: either by the program itself or by the slow database access. For these two possibilities use the transactions SE30 and ST05, respectively.

I wish you an excellent performance improvement,

Heinz

Re: code checking

Former Member — Thu, 27 Mar 2008 07:35:04 GMT

The STAD gives you an overview on the runtime, it will not tell whether the performance is good or bad.

There is anyway nothing which can answer this question. However, the traces tell you whether there is room for improvement. I have written 2 blogs on the SE30 and ST05 which tell you details.

SE30

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

SQL trace:

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

In newer releases there is the code inspector available (tcode sci) which analyzes the coding.

The traces analyze the execution which is always an advantage, but more complicated.

Code Inspector’s Performance Checks (I)

/people/randolf.eilenberger/blog/2007/03/12/code-inspector146s-performance-checks-i

Code Inspector’s Performance Checks (II)

/people/randolf.eilenberger/blog/2007/07/02/code-inspector146s-performance-checks-ii

If you want to process mass data then you should check scalability. For an introduction read

Nonlinearity: The problem and background

/people/siegfried.boes/blog/2007/02/12/performance-problems-caused-by-nonlinear-coding

And the tool to confirm scalability is explained here

Z_SE30_COMPARE

/people/siegfried.boes/blog/2008/01/15/a-tool-to-compare-runtime-measurements-zse30compare

Nonlinearity Check

/people/siegfried.boes/blog/2008/01/24/nonlinearity-check-using-the-zse30compare

Siegfried

Re: code checking

Former Member — Thu, 27 Mar 2008 07:49:15 GMT

Hi ,

Try these Transcation.

ST05 -SLQ TRACE

SE30, -RUN TIME ANALYSIS

SLIN, - EXTENDED PROGRAM CHECK

SCID- CODE INSPECTOR.

reward points if helpfull.