COMMIT and PERFORMANCE and BAPI UPDATE

Question

When looping through  about 10 000 documents it goes initially quite fast but in the end it is very slow. Is it a basis problem?
Initially it takes about 0,5 sec and in the end each document update takes about 20 sec. In total about 15 hours!
My basis consultant says I should do a commit as seldom as possible. But I want to do it after each document (=a LUW?). I could add a counter and do a commit each 100:th document, but I do not like it.
Pseudo logic.
loop at itab (about 20 000 recs)
..CALL FUNCTION 'BAPI_CTRACDOCUMENT_CHANGE'
..Update of a ZTABLE
..COMMIT WORK.
..GET RUNTIME+display RUNTIME-diff
endloop.

Answer 1

Hi mikael,
1. My basis consultant says I should do a commit as seldom as possible
Yes, they are right.
If we don't do commit,
then,
in the database, the rollback area
goes on increasing, increasing,
and occupies memory and gets slow.
2. I could add a counter and do a commit each 100
Thats the best practical solution.
The figure 100 or 50 or 200 etc,
one has to figure out practically.
regards,
amit m.