The existing MergeConfig client API and the MergeObj client API have an argument, Commit frequency. If you are merging large sets of data using the Desktop Client, you can choose to commit in larger data sets by setting the commit frequency argument to tune performance.
If you are merging large sets of data you can choose to commit in larger sets by setting the Commit Frequency argument to tune performance. The default value is set to 50, but the maximum size is limited to 500 to prevent rollbacks or excessive memory usage.
A low Commit Frequency value could make the merge less performant, so the default is set at 50. Increasing the commit value too much could result in excessive memory usage and increase the risk of rolling back many successful merges when an error occurs, so the maximum value is set to 500.
You can merge all the data in one single large transaction by setting the Commit Frequency value to -1. This results in either the Completed or Failed status, and avoids partial merges displayed with the Completed With Errors status.
For more information on the MergeConfig and MergeObj client APIs, see MergeConfig client API and MergeObj client API.