41–50 of 111 posts
That finding might be quite interesting and all... but I'm thoroughly confused about that guy always quoting power consumption in mAh (which is the unit for electrica charge). I'd also check if that guy's dropbox daemon(s) are stuck in an obvious loop. I'm logged on in my private server, and when it's idle there's hardly any activity on the dropbox threads, the main CPU consumer is one servicing what I suspect to be…
Dropbox is terrible with CPU usage. This is something I reported to them several times, but it seems they don't really care. Last I tested, Dropbox consumed CPU for ANY changes ANYWHERE in your filesystem, not just within the Dropbox folder. So its (slow) code processed changes even when you untarred a large set of files somewhere in /tmp. I also stopped using Dropbox for storing my code because of that — it's nearly…
> And to everyone that says you should not store code in dropbox: a) there are good and legitimate reasons for doing so I'm genuinely curious: why do this, as opposed to using a DVCS like git?
I see this problem happening only to me when it's used as code repository. Which is what he is doing. I had that for one project because the client didn't want to use git, but it's horrible. So, logically, when you have a lot of files changing all the time (compiling (xcode, eclipse), adding libraries (node, RoR)) you'll see dropbox taking over your computer. For all other uses it seems fine. Note also that when you…
Well, yes, but if you read the result of his tests even with syncing turned off Dropbox is still eating about 500 mAh. And that is, I would say, rather strange.
Dropbox is terrible with CPU usage. This is something I reported to them several times, but it seems they don't really care. Last I tested, Dropbox consumed CPU for ANY changes ANYWHERE in your filesystem, not just within the Dropbox folder. So its (slow) code processed changes even when you untarred a large set of files somewhere in /tmp. I also stopped using Dropbox for storing my code because of that — it's nearly…
> And to everyone that says you should not store code in dropbox: a) there are good and legitimate reasons for doing so I'm genuinely curious: why do this, as opposed to using a DVCS like git?
The way people generally use source control isn't to push every single line added or changed to a remote copy of the repo as soon as it is done. A commit is more tied to completing a task, you need something else to cover you for loss for smaller amounts of code than that if your computer dies.
Dropbox is terrible with CPU usage. This is something I reported to them several times, but it seems they don't really care. Last I tested, Dropbox consumed CPU for ANY changes ANYWHERE in your filesystem, not just within the Dropbox folder. So its (slow) code processed changes even when you untarred a large set of files somewhere in /tmp. I also stopped using Dropbox for storing my code because of that — it's nearly…
I haven't used Dropbox in a while as a local client for other reasons but I think people need to appreciate this is the payoff for having the convenience? How can one expect it to sync changes if it never scans or detects changes? People seem to want a magical product where it never uses any HD throughput or CPU to index/scan/upload megabytes of data, sure it can look for changes less often but that decreases the usefulness of the product.
As a sidenote, surely all the dropboxers use dropbox for everything (they have unlimited accounts) so they must be 100% aware of this? in which case there must be concrete reasons for this!?
Earlier quoted context omitted.
Dropbox behaves very differently on OSX versus Linux I've found.
likely because linux has inotify
Dropbox is terrible with CPU usage. This is something I reported to them several times, but it seems they don't really care. Last I tested, Dropbox consumed CPU for ANY changes ANYWHERE in your filesystem, not just within the Dropbox folder. So its (slow) code processed changes even when you untarred a large set of files somewhere in /tmp. I also stopped using Dropbox for storing my code because of that — it's nearly…
> And to everyone that says you should not store code in dropbox: a) there are good and legitimate reasons for doing so I'm genuinely curious: why do this, as opposed to using a DVCS like git?
> I use it to store my code repository [...] Not using Dropbox is not an option for me as I switch machines several times during the day. I'd suggest you invest in a hosted git repo.
Earlier quoted context omitted.
> And to everyone that says you should not store code in dropbox: a) there are good and legitimate reasons for doing so I'm genuinely curious: why do this, as opposed to using a DVCS like git?
same question here. If you can get free private git repositories on services like bitbucket, it's sort of a mystery to me why one would want to lose true versioning and go with plain backup instead.
Also, in many cases it is easier for a graphic designer or just a customer to put stuff in a Dropbox folder that will sync to their website, than uploading stuff using a web form or learning to use git and X amount of deployment tools.