|
|
|
|
|
by rarrrrrr
5618 days ago
|
|
Apologies for the support delay. As mentioned above, we have seen overwhelming growth lately and are training support staff to scale up right now. Feel free to mail me directly if I can help. 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. |
|
I don't know about hundreds of thousands of files, but I copied a Django app and CPU usage has been at 100% for a few minutes now. In the end, I closed SpiderOak and I'll turn it on when I'm done.
By the way, do you keep an entire backlog when syncing? I mean, if I use the software for a year and then need to add another computer, will I need to download a year's worth of changesets to get it up to speed?