Copy cloud backup (from copy.com) and CPU usage

[PeterSmith]

It seems that Copy from copy.com (the supposed Dropbox rival, making a splash with the size of its offers of free cloud storage to early adopters) is seriously flawed.

The CPU usage as it watches unchanged folders ("scanning for changes") is about 20% to 30% of a CPU. Compare Dropbox watching the same folders with 0.0% to 0.1%.

Others noted this apparent serious problem???

 

[viizi]

It seems that Copy from copy.com (the supposed Dropbox rival, making a splash with the size of its offers of free cloud storage to early adopters) is seriously flawed.

The CPU usage as it watches unchanged folders ("scanning for changes") is about 20% to 30% of a CPU. Compare Dropbox watching the same folders with 0.0% to 0.1%.

Others noted this apparent serious problem???

I didn't notice but I'd say you are are right. However I did notice that it takes forever to scan for changes compared to dropbox which is almost instant. I am in a dilemma now because I want to choose one online storage for my work but I am torn between dropbox (reliable for years, mature, lower free space) vs copy.com (lots of free space, too early to tell if they are gonna last, any security flaws? their app is messy it seems). Right now I am making do on dropbox but I have my copy.com account idle for future possibilities.

 

[metanoiac]

I am running both copy and dropbox since August 2013 on this machine, and I don't have any problems with either service. Right now dropbox sits at 0.1% of CPU, copy moves from 0.1% to 1.4% of CPU. Mostly also around 0.1-0.3%.

Given that I have all my files synced with copy, copy has to constantly update files, and I am very pleased with its performance. There is the rare occasion that I am working on a huge file (e.g., a 30MB keynote), and in this case I would pause copy until I am done with this file for the day. I mainly do this for saving internet bandwidth - not sure if this is necessary. But other than this, copy runs all the time in the background.

Copy might be busier when you have just installed it. Could this explain your high CPU demands?