The Commit Size determines how many rows are updated (Batch Update) or inserted (Bulk Data) to the database before the transaction is committed. The default Commit Size is 10,000 and is represented as blank in the Masking Job GUI.
This parameter might need to be adjusted depending on the target Database type, Database configuration and Masking Job configuration. In general, it is not required to adjust this value though there are some exceptions.
Below are some examples when this value needs to be adjusted.
Database type and configuration - i.e.
For DB2 the logfile size will determine how many updates/inserts can be held before a commit.
For MS SQL the log size and log mode will determine how many updates/inserts can be held before a commit.
Masking Job configuration - i.e.
No. of Streams, this value defines how many tables are masked at the same time. The value might affect how many updates/inserts held before a commit.
Performance - i.e.
Too frequent (low number) will degrade performance.
Too infrequent (big number) will degrade slightly but will use more resources on the database server.
The best is to run a few Commit Size values and plot the run time to determine which value is optimal.
Please consult your database administrator to determine the most suitable value for your site.