Using the standard variable commit_frequency, you can control the number of times updates are made before the records are committed to the database. A batch program which updates very large numbers of records will often run more efficiently if this facility is used.
One repetition of a procedure body that updates the database is counted as one update. Where more than one table is updated in a procedure body, this still counts as one update.
Do not use this feature in interactive programs or where the auto-increment feature is used
Procedures that secure changes to the database always perform a commit, and so this flag will not affect them.