I didn't read the article but wanted to comment on spideroak: Really love their "realistic" pricing model, even cheaper with a .edu email address. Had a lot of problems with CPU usage, may have been the thousands of files in my .git directories... This leads me to support, they have been overwhelmed and it has been difficult getting then to review my logs. they gave me multiple months free due to my non usage but I d…
I get horrible CPU usage as well. It's to be expected, I guess, since they have to encrypt data, but what is the encryption code written in, Python? Also, it's slow to update things. You wouldn't expect this, given that Linux has inotify, but it is. Their support is rather bad, I've emailed them about legitimate bugs and high CPU usage and SpiderOak not syncing and a whole lot of things, but they never credited me an…
For inotify, the biggest limitation we run into on Linux is that the default system configuration limits a user to watching a relatively small number of folders (6,000 I think, and that includes all subfolders recursively.) You can change this in sysctl if you like, and we may add this change to future packages. In case your curious, the SpiderOak directory watchers are tiny C programs for each platform, and are open source.
FYI -- We've definitely seen high CPU use when syncing hundreds of thousands of small files (source code etc), but this has been greatly improved in the latest beta, which just went out yesterday.
Thanks very much for the feedback.