Nutomic
May 29, 2018, 9:48pm
27
you can work around that by organizing the devices into different tiers. So the supervisors are tier 1, and connected to one or more tier 2 servers each. The tier 2 servers are connected to the actual devices. There are a bunch of topics about this on the forum:
I have 3 nodes at three locations which are always on and do nothing else than run syncthing (300 GB of files).
at each location are a few (1…4) fixed devices which run syncthing to sync parts of the files on the server nodes.
additionally there are about half a dozen mobile devices which are moving between these locations (or other locations connected to the web).
what is the optimal connection between these syncthing servers?
connect all with all (grid - lots of connection)
connect the …
If you are looking for real-time file availability for 1000s of machines, you are looking at the wrong solution and you are probably better off having a shared file system (be it NFS or S3+fuse if you can afford the latency for the scalability).
https://data.syncthing.net/ says there is someone with 2.2k devices, yet I have no idea what their topology looks like, and we target “I run syncthing at home between my N computes” use case (where N is in signle digits), so it’s not something we test f…
https://forum.syncthing.net/search?q=topology
1 Like