[progress Communities] [progress Openedge Abl] Forum Post: Optimal Transaction Size To...

[Lieven De Foor]

Hi Using a FOR EACH EXCLUSIVE-LOCK effectively comes down to a single transaction [er iteration of the FOR loop (assuming there is no transaction active at a higher level). For deleting a large set of records this is noticable slower than grouping records in sets of say 1000 records (in my experiments up to 25% slower). Is there an optimal transaction size for this kind of actions, or a way to calculate an optimal size? Too large increases risk of lock table overflow and possible negative impact on database performance (assumption, please correct me if wrong). Too small lowers performance... I'm not worried about partial results in case of an error (the action is idempotent and can be rerun).

Continue reading...