Performance Tunning

Dear Tigers,


Does any one have the List of rules for Tunning a routine. Rather is there any statndard procedure for performance tunning. Any documents, info about this is welcome...
_________________
NJOY LIFE TO THE FULLEST

Hi Iron,

In my opinion, most of the codes in GLOBUS were not atall undergone performance testing. But even temenos has given some set of standards for tuning the performance. Here are below.

Coding Standards

1. A template routine should not exceed 2000 lines.
2. A call subroutine should not exceed 600 lines.
3. A GOSUB block should not exceed 100 lines.
4. A IF condition block shoud not exceed 60 lines.

Performance Tuning

1. FOR..NEXT should be replaced with LOOP..REMOVE ( if applicable).
2. EXECUTE or PERFORM should be replaced with CALL ( if applicable). Because it will create its own memory space.
3. In some cases READ is better than F.READ and WRITE is better than F.WRITE.
4. Dont put big codes between a TRANSSTART and TRANSEND.
5. While developing BATCH programs use multithreading (SELECT,LOAD...)
6. In jbase we have 1 utility 'jprof' which tells which part of code consumes how much amount of time.

Still many more...
If I am not wrong, there is no documents telling this.
_________________
M A L A I

Hi Malai,

Also to add upon

SELECT Statment

---

SELECT <FileVariable> is faster than EXECUTE 'SELECT ....' which is faster that our famous EB.READLIST

OPEN Statement

---

Multiple OPEN statments with LOOP or FOR conditions. This will also cause performance issue.

Some codings standards are
Use decrement instead of increment
Use i =+1 format instead of i = i + 1

I will update these standards As and when i come across
_________________
NJOY LIFE TO THE FULLEST

Hi

I got some more.

don't use DBR especially in a loop and avoid EB.PRINT to create reports.
_________________
M A L A I