Syncthing is being used to sync crazy amounts of data already (see the stats link from schnappijedi above), and has been doing so for years. This reduces network traffic and increases speed in comparison to webdav. Syncthing syncs file deltas, not whole files. You can also set up your own discovery server, the source for this is also available. All this does is put the instances in contact with each other (no data goes through the discover server). Syncthing also has a discovery server to help syncthing instances connect to each other when not on the same LAN. If they are not on the same LAN they sync over the internet. If the instances are on the same LAN, they notice this and sync directly over LAN. Connections are made directly between synthing instances, there is no central server. The syncthing protocol is decentralised, it does LANSync by default. I'm not sure these were actually answered, but just to spell it out. Syncthing is the closet thing to cross platform real time rsync.Īgain though Syncthing can be fairly easily integrated into Nextcloud as it is. Both protocols will max out bandwidth eventually during a sync but Syncthing will start utilizing max bandwidth faster than webdav. Better put webdav is not a fast protocol (notwithstanding anything to do with how fast the Syncthing sync protocl is). The Syncthing sync protocol is faster than webdav. Syncthing also for example can sync huge changed files without needing to reupload the entire file (delta sync). Syncthing works reliably when resuming extremely large file uploads or downloads. Obviously causing issues for laptops and other machines not on 24/7 and making webdav unusable for large files. Even assuming a server is configured correctly for very large files a webdav upload or download will restart when a client goes offline. The sync protocol in Syncthing is far superior to webdav. The top end of devices reporting show over 100,000 GB being shared in 4k folders over 2,000 devices. The statistics here show opt-in usage data. Theoretically the config setting below can also be used (0 is default) instead of using external local folders but have not tried or tested this:Įxternal local folders integrating Syncthing works great. One either has to run the nextcloud commandīut this takes far to long to do this on a regular minute by minute basis for large folders or set all folders shared with Syncthing as external local folders in Nextcloud which will cause changes made by Syncthing to be picked up immediately in Nextcloud. Secondly changes made by Syncthing will not be picked up in Nextcloud folders by default. That being said one can set the custom folder path of Syncthing versioning to be the same as Nextcloud trash (nextcloud/data/user/files_trashbin). Syncthing needs to be run as Syncthing will not utilize the Nextcloud trash or versions folder by default.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |