SourceTree UI refresh lag during large-scale conflict resolution

SourceTree utilizes a proprietary interface for resolving Git merge conflicts, allowing users to select 'Mine' or 'Theirs' versions for individual files. When processing a commit tree containing hundreds of conflicted files, the application attempts to refresh the status of each item simultaneously within the UI.

There is a documented inconsistency regarding how the UI reflects 'partial stages' during complex rebasing operations. In some instances, the index state does not update immediately after an action is taken, necessitating a manual interface refresh to synchronize the visual state with the actual Git index.

What is the specific threshold of conflicted files where the UI thread begins to experience significant latency during status updates? Is there a configuration setting to disable automatic status refreshes during high-volume merges to prevent performance degradation?