Dropbox is in my opinion synonymous with poor performance. The client always consumed way too much CPU. On a Mac, Dropbox will react to changes anywhere in the filesystem, and consume excessive amounts of CPU even if the files you work on have nothing to do with Dropbox. If you use selective sync, stuff that lands in folders <i>not synced</i> to your computer will still cause Dropbox to consume CPU.<p>Storing a lot of files inside your Dropbox will also cause performance problems. Which means that paying for extra space (I do) isn&#x27;t that useful if you intend to keep your git repos with source code there.<p>It has been like that for years, the company has made little progress performance-wise (instead we got useless things like photo-something-or-other-that-tries-to-access-my-photos).<p>I learned to live with it, because the advantages of Dropbox outweigh the disadvantages of a poor implementation. Dropbox is still a very good product, even if you have to pay a hefty price in CPU and battery life for it. I dream that one day someone will decide that performance is a goal worth pursuing and finally optimize the thing.