5 ms·
any good?
by samwestdev 11y ago
any good?
- jhasse 11y agoYes! But it's decentralized. An alternative to Ubuntu One would be ownCloud (https://owncloud.org/ https://owncloud.org/).
- bildung 11y agoAnother alternative is Seafile https://www.seafile.com/en/download/ https://www.seafile.com/en/download/
- mrschwabe 11y agoAnd yet another alternative, nodejs based: http://cozy.io http://cozy.io
- ef4 11y agoCentralized is just a degenerate case of decentralized. Stand up a dedicated server running syncthing and poof!, you have a centralized syncthing.
- baldfat 11y agosynch Thing is really a good option. It has a good community that is actively supporting the product and the features include only syncing certain files is great. I was a former Bit Torret Sync user but switch due to its open source code.
- deleted 11y ago[deleted]
- rocky1138 11y agoYes. It's very good. I've been using it for about 4 months now between a Raspberry Pi (Raspbian Linux), an old laptop (Ubuntu Linux), my main computer (Windows 8.1), and my girlfriend's computer (Windows 8.1).
- pedrocr 11y agoIt's usable if you have a small amount of files. For anything serious (say 100k files or 500GB of data) is blows through CPU and RAM to the point of being unusable. I've been actively testing several and there is currently no actually good open-source solution in this space.
- rocky1138 11y agoI've got about 150GB (but well over 100k files) and it only really lags on the Raspberry Pi. One thing I could suggest is that you change how often it rescans your directories for changes (I set mine to 6000 seconds versus the default 60). That might make a difference.
- pedrocr 11y agoI've explored this pretty extensively and it's currently just the way it is. It happens from first sync so the rescan interval makes no difference. Your collection probably requires 300-400MB of RAM to sync so it should be on the cusp of failing on a raspberry pi. Here's the bug report that was closed without any fix: https://github.com/syncthing/syncthing/issues/468 https://github.com/syncthing/syncthing/issues/468 And user reports of this show up pretty often: https://github.com/syncthing/syncthing/issues/1841 https://github.com/syncthing/syncthing/issues/1841 https://forum.syncthing.net/t/arm-linux-cpu-usage-99-for-many-hours-with-no-progress-on-syncing/5322 https://forum.syncthing.net/t/arm-linux-cpu-usage-99-for-man... https://github.com/syncthing/syncthing/issues/1841 https://github.com/syncthing/syncthing/issues/1841 A sync tool that uses on the order 2MB of RAM per GB of files or 4kB per file isn't really usable. A cheap NAS these days can easily have 6TB of RAID6 storage but it won't have 12GB of RAM. Clearly something in syncthing is keeping way too much stuff pinned in memory and the developers so far haven't focused on that. There's no apparent need for this memory usage either as there's already an on-disk database with the state of the sync folder.
- rocky1138 11y agoThat's really interesting, thanks.
- stewbrew 11y agoYes. It's easy to install and runs on Android. It's quite fast in detecting differences and then syncing 2 nodes. It's meant to permanently run in the background though. It cannot be not easyly automated to, eg, sync 2 nodes and then shut down. In case if concurrent edits, you end up with multiple versions of the file on disk. You have to somehow detect those conflicts (find) and merge the files yourself. It doesn't help you much with that.