Dreamweaver UI becomes non‑responsive during site‑wide find‑and‑replace

Goal: Determine whether concurrent file‑access operations exacerbate the UI latency observed during a site‑wide find‑and‑replace in Adobe Dreamweaver, and identify any configurable thresholds that could mitigate the block.

Constraints: The latency is known to increase when the find‑and‑replace uses regular expressions or targets files on network drives, but it is unclear whether simultaneous read/write activity from other processes or Dreamweaver features (such as live preview or FTP sync) adds additional strain on the UI thread, potentially leading to a non‑responsive state.

• Does limiting the number of concurrent file‑access threads in Dreamweaver reduce UI blocking?
• Can increasing the timeout for background file I/O improve responsiveness during large find‑and‑replace?
• Is there a preference or registry setting to offload the find‑and‑replace operation to a worker thread so the UI remains interactive?