Solved: performance tunning

Former Member · ‎2007 Jul 16

hi,

In performance tunning

how wiil help "CHECK" instead of IF/ENDIF and "CASE" instead of IF/ENDIF

Thank you

ASHOK KUMAR

seshatalpasai_madala · ‎2007 Jul 16

Hi,

Check in debug mode when you are using IF ENDIF if the condition is false in a LOOP ENDLOOP, you will still goto ENDLOOP statement and then back to LOOP. Where as when you use CHECK its again back to LOOP statement.

CHECK is very usfeul when you want ALL THAT CODE BELOW THE CHECK statement to be executed only when the condition is correct.

So when you use CHECK it will come out of the current loop pass and continues with the next loop pass.

WHERE as IF is like next statements will be checked. or executed.

CHECK Is more useful but needs to be used carefully as it skips all the code after that.

Regards,

Sesh

seshatalpasai_madala · ‎2007 Jul 16

Hi,

Check in debug mode when you are using IF ENDIF if the condition is false in a LOOP ENDLOOP, you will still goto ENDLOOP statement and then back to LOOP. Where as when you use CHECK its again back to LOOP statement.

CHECK is very usfeul when you want ALL THAT CODE BELOW THE CHECK statement to be executed only when the condition is correct.

So when you use CHECK it will come out of the current loop pass and continues with the next loop pass.

WHERE as IF is like next statements will be checked. or executed.

CHECK Is more useful but needs to be used carefully as it skips all the code after that.

Regards,

Sesh

Former Member · ‎2007 Jul 16

Hi

instead of writing multiple IF/ENDIF it is better to write CASE...WHEN..ENDCASE.

Betetr not to use CHECK use if..

If it is one or two or three times it doesn't effect the performance much

say if there are some 30 if..endif statements it looks ackward and ugly to see so many if..endif..and performance also not so good

see the doc

1) Dont use nested select statements

2) If possible use for all entries in addition

3) In the where addition make sure you give all the primary key

4) Use Index for the selection criteria.

5) You can also use inner joins

6) You can try to put the data from the first select statement into an Itab and then in order to select the data from the second table use for all entries in.

7) Use the runtime analysis SE30 and SQL Trace (ST05) to identify the performance and also to identify where the load is heavy, so that you can change the code accordingly

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d0db4c9-0e01-0010-b68f-9b1...

ABAP performance depends upon various factors and in devicded in three parts:

1. Database

2. ABAP

3. System

Run Any program using SE30 (performance analys) to improve performance refer to tips and trics section of SE30, Always remember that ABAP perfirmance is improved when there is least load on Database.

u can get an interactive grap in SE30 regarding this with a file.

also if u find runtime of parts of codes then use :

Switch on RTA Dynamically within ABAP Code

*To turn runtim analysis on within ABAP code insert the following code

SET RUN TIME ANALYZER ON.

*To turn runtim analysis off within ABAP code insert the following code

SET RUN TIME ANALYZER OFF.

Always check the driver internal tables is not empty, while using FOR ALL ENTRIES

Avoid for all entries in JOINS

Try to avoid joins and use FOR ALL ENTRIES.

Try to restrict the joins to 1 level only ie only for tables

Avoid using Select *.