[prepend]

I have free OneDrive through my university, and I pay $99/year and I have it through work. With multiple TB available.

Yet I still use Dropbox because it’s way more usable.

Running the OneDrive agent is a hobby and it spikes my machine a few times a day. Running Dropbox is something that just works and has worked for 10 years without me ever noticing the sync app (a good thing).

I avoid Google because I wouldn’t want my gmail to turn off because of an event like this.

[vikingerik]

How do you never notice the sync app? I stopped using Dropbox because I got sick of the client (on Windows) constantly blaring about new features and corporate sharing tools.

[prepend]

I muted that stuff years ago and have it run on startup. I get no notifications and if I put a file in that folder it syncs up. And files I add to dropbox sync down.

Granted I haven’t run the windows client in a long time so I’m talking about my MacOS experience. But OneDrive on MacOS does all sorts of shenanigans. The funniest is when it logs me out and forces a hard resync. As a user, I never want that.

[beebmam]

Never had any CPU spikes from OneDrive. How much are you storing on it?

[prepend]

It’s hard to tell, but I think 195GB in the cloud and 44GB on my typical workstation.

I run on MacOS and my cpu has spiked twice today already. When I hear the fans, it’s usually OneDrive.

I don’t mind the cpu as I have lots but it might take 30 seconds to sync a new word document before I can share it, so that’s annoying.

With Dropbox it’s almost instantaneous and the file just syncs up.

I’m not sure what OneDrive is doing, but it’s harder to use. I don’t want to slow down and wait for OneDrive to sync before I work with others.

[Espressosaurus]

The more files you have, the more OneDrive tends to chew as a baseline. If you exceed those limits it'll just sit and chew without actually updating anymore. I want to say something like 200K files is the limit.

If you're using it for work to sync build dependencies or your build tree or similar, it's easy to accidentally end up exceeding those limits and watch it eat CPU time totally ineffectually. Ask me how I know!