This is a follow-up to my previous post about private cloud sync software. I would advise you to read it here first before reading this.
I spent this past week in Alabama and naturally had to travel to and from there. I thought this would be a great time to evaluate the two sync software I previously mentioned, BitTorrent Sync and AeroFS, in less controlled environments. This includes airport wifi, hotel wifi, and corporate network.
My gut feeling going into these travels was that BitTorrent Sync wouldn’t work in a few places since it’s, well, BitTorrent. In practice this was completely untrue. It worked on every network I put it on during my travels and transferred at a speed the network allowed. If you have crappy bandwidth available then BitTorrent Sync will obviously fall victim to it. It pretty much just worked and through some casual examination it appears as though it did indeed choose the best “route” possible at all times.
AeroFS on the other hand was a disappointment. It doesn’t appear to handle network changes well or even lack of network connectivity in the first place. I was sitting in an airport not connected to wifi and noticed it was using 10-15% CPU doing nothing. It also doesn’t seem to react to network changes in a speedy manner. I would find it using a relay for transfers when I would expect LAN or WAN to be used until a sufficient amount of time had passed and then subsequent transfers would use the expected method.
In the end…
I continue to use BitTorrent Sync and have removed AeroFS from my systems. I currently use a configuration where I sync one “BitTorrent Sync” folder with stuff inside of it, but may split it up some more. We’ll see!