45 ms·

Unfortunately, in my experience using Syncthing while doing cross-platform development (coding on a Mac, compiling and testing on a Windows machine, both machin

by oefrha 7y ago

Unfortunately, in my experience using Syncthing while doing cross-platform development (coding on a Mac, compiling and testing on a Windows machine, both machines connected to the same Ethernet switch and sitting right next to each other), syncing with Syncthing is far from instant. If you just want a cheap Markdown editor with instant syncing, I recommend self-hosted CodiMD. Of course that’s not an option if you actually want the full power of org-mode.

StavrosK 7y ago
That's odd, it's pretty instant for me. I've been an extremely happy user for years.
- oefrha 7y ago
  Not sure if it has anything to do with file count. I sync a couple thousand files in a directory with close to a million files (aggressively ignored most), although I was talking about changing one file at a time and having the change show up on the other machine maybe 15 to 20 seconds later — or longer, can’t recall exactly. Scanning is very slow too (this is on a fast SSD).
  - StavrosK 7y ago
    Hmm, that's definitely not typical for me, it only takes a second or two for files to show up. It should be using inotify to be notified of changes, but I don't know if there's a difference on OS X (I'm on Linux).
    - oefrha 7y ago
      My experience has been on macOS and Windows, slow both ways. I haven’t used it on Linux. On macOS FSEvents or kqueue can be used, I’m not sure which one is used. They are definitely using a notification mechanism though, otherwise changes won’t even happen in 15s.
      - StavrosK 7y ago
        Have you checked "Monitor filesystem for changes" in the config? It polls if you don't do that, and I think it doesn't get checked by default, but I'm not sure.
        oefrha 7y ago
        Yes, "watch for changes" is on for all my synced directories, and on by default. According to https://docs.syncthing.net/users/syncing.html https://docs.syncthing.net/users/syncing.html > There are two methods how Syncthing detects changes: By regular full scans and by notifications received from the filesystem (“watcher”). By default the watcher is enabled and full scans are done once per hour.

by oefrha 7y ago

StavrosK 7y ago

That's odd, it's pretty instant for me. I've been an extremely happy user for years.

oefrha 7y ago
Not sure if it has anything to do with file count. I sync a couple thousand files in a directory with close to a million files (aggressively ignored most), although I was talking about changing one file at a time and having the change show up on the other machine maybe 15 to 20 seconds later — or longer, can’t recall exactly. Scanning is very slow too (this is on a fast SSD).
- StavrosK 7y ago
  Hmm, that's definitely not typical for me, it only takes a second or two for files to show up. It should be using inotify to be notified of changes, but I don't know if there's a difference on OS X (I'm on Linux).
  - oefrha 7y ago
    My experience has been on macOS and Windows, slow both ways. I haven’t used it on Linux. On macOS FSEvents or kqueue can be used, I’m not sure which one is used. They are definitely using a notification mechanism though, otherwise changes won’t even happen in 15s.
    - StavrosK 7y ago
      Have you checked "Monitor filesystem for changes" in the config? It polls if you don't do that, and I think it doesn't get checked by default, but I'm not sure.
      - oefrha 7y ago
        Yes, "watch for changes" is on for all my synced directories, and on by default. According to https://docs.syncthing.net/users/syncing.html https://docs.syncthing.net/users/syncing.html > There are two methods how Syncthing detects changes: By regular full scans and by notifications received from the filesystem (“watcher”). By default the watcher is enabled and full scans are done once per hour.