I have been using this tool for remote development on a big project, which contains a frequently-altered directory, say local-data. I put it in the ignores field in my config and am sure delta transmission is on. However, there is still a very high network flow even though there is no change in my project (of course, except for the directories I have ignored).
Then I analyzed the log and finally found that it is because the ignores field is only passed to rsync, but not the directory watcher. So it thinks my project is altered every second and does rsync very frequently, which causes high metadata transmission(although there is no real data transmitted, it is still very large!).
A possible fix may be to pass the ignore field not only to rsync, but also to the directory watcher.
I have been using this tool for remote development on a big project, which contains a frequently-altered directory, say
local-data. I put it in theignoresfield in my config and am sure delta transmission is on. However, there is still a very high network flow even though there is no change in my project (of course, except for the directories I have ignored).Then I analyzed the log and finally found that it is because the
ignoresfield is only passed torsync, but not the directory watcher. So it thinks my project is altered every second and doesrsyncvery frequently, which causes high metadata transmission(although there is no real data transmitted, it is still very large!).A possible fix may be to pass the
ignorefield not only torsync, but also to the directory watcher.