Idea: upload/download status; general usability

Hi Steffen,

Thank you for taking the time to make these suggestions. In our latest client (in Lucid and our PPA), there are two main user visible ways you can see the status of syncing: 1) overall syncing is displayed in the ubuntuone-preferences application which is found either in the Lucid Me menu or System->Preferences->Ubuntu One 2) file emblems should notify the status of syncing on a per file/folder basis. We will be looking to improve these status indicators in the next version of Ubuntu (Maverick) and will take your suggestions into consideration.

Thank you,

Joshua

id like to stress a point steffen mentioned before. sometimes theres a message displayed that the client is up/down loading files without any changes made. another thing that intrests me is how changes on the same file are being handled - after sharing and both are changeing the file.
besides theres quite some activity for beam and many wakes for ubuntuone client (like 0,1-1% CPU usage)
somehow it seems to lack a summary of files and change dates respectively. ubuntuone should ONLY be active if that summary of files is being changed either on the server or on any of the clients using shared files, and therefore uploading to the server, or in other words only on write actions. so it should sleep until any trigger activates it. scanning for changes as it seems (maybe im wrong there) is not a good solution.

thanks for the work done and hoping for the feedback to be appreciated!
regards
jakub
(im using natty)

On 02/20/2011 10:32 AM, Jakub Orlowski wrote:
> Question #106364 on Ubuntu One Client changed:
> https://answers.launchpad.net/ubuntuone-client/+question/106364
>
> Jakub Orlowski posted a new comment:
> id like to stress a point steffen mentioned before. sometimes theres a message displayed that the client is up/down loading files without any changes made. another thing that intrests me is how changes on the same file are being handled - after sharing and both are changeing the file.
> besides theres quite some activity for beam and many wakes for ubuntuone client (like 0,1-1% CPU usage)
> somehow it seems to lack a summary of files and change dates respectively. ubuntuone should ONLY be active if that summary of files is being changed either on the server or on any of the clients using shared files, and therefore uploading to the server, or in other words only on write actions. so it should sleep until any trigger activates it. scanning for changes as it seems (maybe im wrong there) is not a good solution.
>

The Ubuntu One client only scans for changes when it first starts. After that it uses pynotify to detect file changes.
Recent changes to the Ubuntu One client (I'm using nightlies) has improved the scanning process quite a bit. I have 15k
files and it scans my files within a couple of minutes.

minutes???
is last change date not reasonable? it would only take to check 15k dates on relogging to server for updating and only access would be on write.. isnt that good enough?
i mean.... 15k dates would not even take half a second would it? maybe theres something more important that is yet unknown to me, but in fact why should it be much different from synaptic updating packages? cant it be reused?

On 02/20/2011 02:12 PM, Jakub Orlowski wrote:
> Question #106364 on Ubuntu One Client changed:
> https://answers.launchpad.net/ubuntuone-client/+question/106364
>
> Jakub Orlowski proposed the following answer:
> minutes???
> is last change date not reasonable? it would only take to check 15k dates on relogging to server for updating and only access would be on write.. isnt that good enough?
> i mean.... 15k dates would not even take half a second would it? maybe theres something more important that is yet unknown to me, but in fact why should it be much different from synaptic updating packages? cant it be reused?
>

So the numbers I gave you were misleading and inexact as they included more than just a local rescan, which is what you
were looking for. As you can see below, The local rescan took seconds. The entire process including connecting to the
server 'server rescan' took less than one minute.

16:46:41,572 : Client Start (first record in syncdaemon.log)
16:46:41,572 : Start Loading local metadata
16:46:42,522 : Local Metadata loaded
16:46:44,591 : Local Rescan Started
16:47:15,453 : Local Rescan Finished
16:47:16,655 : Server Rescan Started
16:47:18,216 : Server Rescan Finished
16:47:18,763 <--- IDLE

still beam is never under 2,4% CPU usage on my system
maybe its a bug...
(on a 1,6GHz Laptop which seems not to be very much capable of using different steppings in ubuntu!!!)

Jakub,

The beam.smp process is not related with the file sync daemon but with desktopcouch, to be precise that is couchdb running. Please take a look at lp:458453