commit work and performanceproblem

[Former Member]

Hi,

Setting Commit Works in Abap arise performanceproblem?

How is it to explain?

Thanks!

Beserithan Malabakan

[Former Member]

Commit work can become a performance bottleneck if there are many updates being carried out in the loop...say in terms of 1000's. The solution for that is to use commit work after say 100/200 updates.

Regards

Anurag

[Former Member]

Hi,

Generally a COMMIT work is done in update task. WHich is then done in a separate V1 an V2 work process.

Triggering Commit work in the ABAP explicitly will cause the system to trigger the commit in local task or in the same workprocess.

Cheers

VJ

[Former Member]

The changes we make to the database are temporarily stored in the buffer until and unless we use a commit or the system automatically commits them.

If we use the commit work statement, then it will take extra time to write the changes in the buffer to the database.

So we have to use commit statements only when it is absolutely necessary.

Regards,

Ravi

[Former Member]

we have set Commit work after Update Function Modules

and after we have inserted Records in database table.

If Single User works with application there is no Performanceproblem But with 10 user we become performanceproblem?This means Commit works make closes database table for one User and set the Records into table.Is that true?

B.M.

[Former Member]

Basically, they way it would be is that during the update task the corresponding table/record is locked and surely, if you have 10 users trying to update the same table there would be a delay !!!

Regards

Anurag

[Former Member]

Thanks a lot for all Replies.

B.M.