Is file watching disabled? If not, then there should be no reason to use such a low scan interval. Even if file watching is disabled or not working for some reason, the default scan interval in such a case is automatically set to 60s for a reason. If you use a very low value like 3s or 5s, this will make the folder being scanned constantly, just wasting resources.
@tomasz86 afaik i remember i choosed the low value because the “on-demand / filewatcher” was slow on windows server 2025. So i changed to 3s or now 5s.
So you mean thats not necesarry? Then i will it with maybe 30sec.
@chaos Were i can check watcher settings? I’m using win-server 2025 standard.
Tested it quickly. Thats very slow. File sync needs between 5-15sec. Thats too long. I need it almost instantly if this is possible. How i can improve the watcher?
Yes, but you need to go down into per-folder settings. If you want instant synchronisation, you can set the watcher to a value like 0.1. Please keep in mind that there will be some performance impact when using such low values.
thank you so much. Didn’t saw that before.
2s was still to slow. Sometimes the watcher/sync needs over 5sec.
I changed now to 1s which looks good so far.
Performance is still not that good since ~1-2weeks. Bandwith is stable and 1GBit each server (3 in the cluster).
Will oberserve a bit this week and let you know. Thanks!