This screenshot shows that few minutes after having opened the desktop session, after startup application have initialized, ubuntuone-syncdaemon is still hashing and consumes lot of resources.
The size of files in my Ubuntu One account is about 300M each, which is a possible explanation for such a long time spent in hashing. However I tried this command to get a hash value of one of these files on the same computer:
$ time sha1sum 300.mega.bytes.file
9ee2e5689ece78a5644aa357597473cb127a7e4c 300.mega.bytes.file
real 0m12.493s
user 0m3.976s
sys 0m8.189s
And I get a result in 12s, which makes me think that the right solution for ubuntuone-syncdaemon could be not only executing with a higher nice value, but also using a less time consuming hashing algorithm.
This screenshot shows that few minutes after having opened the desktop session, after startup application have initialized, ubuntuone- syncdaemon is still hashing and consumes lot of resources.
The size of files in my Ubuntu One account is about 300M each, which is a possible explanation for such a long time spent in hashing. However I tried this command to get a hash value of one of these files on the same computer:
$ time sha1sum 300.mega.bytes.file 5644aa357597473 cb127a7e4c 300.mega.bytes.file
9ee2e5689ece78a
real 0m12.493s
user 0m3.976s
sys 0m8.189s
And I get a result in 12s, which makes me think that the right solution for ubuntuone- syncdaemon could be not only executing with a higher nice value, but also using a less time consuming hashing algorithm.
Cheers.