3 ms·

I'm almost certainly an edge case, I just migrated off BTSync. I was using it to automatically back up my docs/code/photos etc from my laptop to my low-power NA

by de_dave 12y ago

I'm almost certainly an edge case, I just migrated off BTSync. I was using it to automatically back up my docs/code/photos etc from my laptop to my low-power NAS, but the CPU overhead was just not worth it. (NAS was frequently pegged at 100% CPU dealing solely with BTSync). Switched to using lsyncd instead, and works a treat! That said, BTSync was fantastic when it worked, and Syncthing looks incredibly promising, too.

domainkiller 12y ago
I've currently (slowly) migrating from Dropbox and BTSync to Syncthing. I'd say you might have a glitch in the matrix if BTSync is running that high without any active transfers.
- 0x5f3759df-i 12y ago
  I'm completely switched over to Syncthing/Pulse or whatever they're calling it now. I have no trust for a proprietary "cloud" with my data.
  - de_dave 12y ago
    Would love it if Pulse had the option to encrypt the stored data (currently it only encrypts during transmission), so it could be used on untrusted hosts.
    - eli 12y ago
      Yeah, definitely. It would be a lot easier to have multiple redundant copies of my data if I didn't have to worry about securing each one. It's one of the main reasons I picked Duplicity for backup.
- de_dave 12y ago
  On my (already battery-starved) laptop, it would always suck up 100% CPU for a few minutes on a fresh boot, and then occasionally pop up now and again. On my (PowerPC!) NAS, it was constantly using lots of CPU and RAM, although I have a feeling plenty of that was caused by swapping to disk (NAS only has 128MB). I love the fact that BTSync have the forethought to provide a PowerPC client for people with outmoded NAS's like mine, just disappointed it was still too heavy to work reliably.
mikehearn 12y ago
I'm in the same situation with the OS X client. I was using BTSync + Arc to essentially match Dropbox's feature set, but in the past couple of months BTSync seemingly lost its mind with respect to CPU usage. It would routinely hit 100% and would always show up on OS X's "Apps Using Significant Energy" list. I had to shut it down so often that it ultimately wasn't worth it. I switched back to Dropbox and abandoned any sort of privacy once again.

by de_dave 12y ago

domainkiller 12y ago

I've currently (slowly) migrating from Dropbox and BTSync to Syncthing. I'd say you might have a glitch in the matrix if BTSync is running that high without any active transfers.

0x5f3759df-i 12y ago
I'm completely switched over to Syncthing/Pulse or whatever they're calling it now. I have no trust for a proprietary "cloud" with my data.
- de_dave 12y ago
  Would love it if Pulse had the option to encrypt the stored data (currently it only encrypts during transmission), so it could be used on untrusted hosts.
  - eli 12y ago
    Yeah, definitely. It would be a lot easier to have multiple redundant copies of my data if I didn't have to worry about securing each one. It's one of the main reasons I picked Duplicity for backup.
de_dave 12y ago
On my (already battery-starved) laptop, it would always suck up 100% CPU for a few minutes on a fresh boot, and then occasionally pop up now and again. On my (PowerPC!) NAS, it was constantly using lots of CPU and RAM, although I have a feeling plenty of that was caused by swapping to disk (NAS only has 128MB). I love the fact that BTSync have the forethought to provide a PowerPC client for people with outmoded NAS's like mine, just disappointed it was still too heavy to work reliably.

mikehearn 12y ago

I'm in the same situation with the OS X client. I was using BTSync + Arc to essentially match Dropbox's feature set, but in the past couple of months BTSync seemingly lost its mind with respect to CPU usage. It would routinely hit 100% and would always show up on OS X's "Apps Using Significant Energy" list. I had to shut it down so often that it ultimately wasn't worth it. I switched back to Dropbox and abandoned any sort of privacy once again.