Gradle File System Watcher latency during concurrent background syncs

Android Studio utilizes the Gradle File System Watcher to monitor project changes and trigger incremental builds or indexing tasks. However, when multiple concurrent build requests or background syncs are initiated simultaneously, significant UI lag often occurs during the re-indexing process.

This contention appears to stem from high-frequency file events overwhelming the UI thread's ability to process updates without blocking. While parallel execution is enabled to speed up module compilation, the overhead of tracking rapid file changes under heavy load seems to saturate the IDE's responsiveness, leading to intermittent unresponsive behavior in resource-constrained environments.

Is there a specific configuration to limit the priority of the File System Watcher relative to UI responsiveness during concurrent tasks? How can the IDE differentiate between critical build-related file changes and transient background process noise to prevent re-indexing bottlenecks?