"Settle" behavior blocks entire file tree during long running zip operation
vincesp opened this issue · comments
The default settle period is 20 ms. This is long enough so that the entire tree below each root is blocked as long as a single zip operation is running inside it – or any other long operation that streams to a file.
Is there a way to circumvent this?
Creating a .watchmanconfig file at the root and setting settle to 3 ms fixes the issue. But it makes watchman very "chatty" and the UI client will perform many more updates that could be avoided.
Could the "settle" algorithm improved, e.g., by always "forcing" an update after 200 ms latest?