Uses up power while travelling

Please reassign as appropriate.

we should try to get power status from Power Manager (or the equivalent) and do things differently when on battery than when on Mains. For instance, sync should be a manual thing. Possibly this could be configurable as well (if, for instance the user places priority on sync rather than battery life.

Similar to the power profiles that can be set...

On Thu, 2009-06-11 at 18:14 +0000, Rick McBride wrote:
> we should try to get power status from Power Manager (or the equivalent)
> and do things differently when on battery than when on Mains. For
> instance, sync should be a manual thing. Possibly this could be
> configurable as well (if, for instance the user places priority on sync
> rather than battery life.
>
> Similar to the power profiles that can be set...

When I observed this behaviour I had no network either. No matter the
priority on sync, with no network and no UI open on the ubuntu one
shares its hard to justify 5% of wakeups from the syncdaemon.

I agree that there may be a need to let people choose what they want;
however I think it would be nicer to just choose good defaults before
worrying about customisation.

-Rob

Robert Collins wrote:
> On Thu, 2009-06-11 at 18:14 +0000, Rick McBride wrote:
>> we should try to get power status from Power Manager (or the equivalent)
>> and do things differently when on battery than when on Mains. For
>> instance, sync should be a manual thing. Possibly this could be
>> configurable as well (if, for instance the user places priority on sync
>> rather than battery life.
>>
>> Similar to the power profiles that can be set...
>
> When I observed this behaviour I had no network either. No matter the
> priority on sync, with no network and no UI open on the ubuntu one
> shares its hard to justify 5% of wakeups from the syncdaemon.
>
> I agree that there may be a need to let people choose what they want;
> however I think it would be nicer to just choose good defaults before
> worrying about customisation.
>
> -Rob
>

Agreed. Good defaults come first, and customization later.

I'm currently spotting 10 wakeups/sec for ubuntuone-synced and 10 wakeups/sec for ubuntuone-client, when idle.

Dropbox, as a comparison (since it's the only similar application that I know of), only causes nautilus to show 10 wakeups/sec, and this is only if the nautilus plugin is being used. The dropbox daemon itself shows <1 wakeup/sec here.

Note that even without the nautilus plugin, the daemon works as it should. The only drawback is that there are no emblems used in nautilus under the Dropbox directory.

It is one wakeup per second for ubuntuone-client and ubuntuone-synced here. (it sais 10, but its interval is 10s).

Why does it wake up more then once per second to begin with? I cannot see a reason for this. (FS can be monitored using inotify or eq and i highly doubt it checks the online part is queried that often. )

Rick re: "we should try to do things differently when on battery than when on Mains".

If I'm living on a boat, my "mains" is just a bunch more batteries (admittedly bigger ones); if the wind hasn't blown, or the sun hasn't shone, there might not be very much of it! ...If it's possible to avoid doing something on battery in order to save power, it's probably possible to avoid doing it on mains too! (Which saves energy, reduces heat output and allows more power to be diverted to recharging the laptop's internal batteries).

Agree..
We don't need 2 different profiles for batteries and for mains.
We need one effective profile that works all time. (We have to start thinking a bit green)
If all wakeups are send thru the network to the servers it also causes more load on the servers.
If not...they are not needed

Is there any updates with this bug?

Hi Rodney,

I see a commit linked to this bug report, and it should have been released a while ago. So I don't know why you returned it to confirmed. I'll mark it as fix released, but feel free to reopen it telling us why :)

pura vida.

Leo, yes there was a commit a long time ago. However, it did not fix the problem, and actually made it much worse. That change was reverted very shortly after it landed. However, this is a known issue with twisted, and there are several reports on the problem. This should probably be marked as a duplicate of one of the others. It is fixed in twisted trunk, and should make it into Precise, and we will backport the fix for older versions of Ubuntu, once it is.

Great, thanks for the explanation Rodney.
If I find the other reports I'll mark it as duplicate.

Hug.