upowerd consuming one whole core if battery low

[Václav Krpec]

Hi Bastien,

you are right; the polling looks the same as now (I started to charge,
so the problem disappears).
However, I notice something else that is quite different:
the amount of writing to /var/lib/upower/history- files.
And quite substantial amounts of data, judging from the allocations.
Is that normal?

Thanks,

vencik



On Wed, 2014-07-02 at 12:51 +0200, Bastien Nocera wrote:
> On Wed, 2014-07-02 at 12:09 +0200, Václav Krpec wrote:
> > Hello everybody,
> > 
> > as a follow-up of the previous post, this time I include
> > strace log.
> > upower seems to read battery info in busy loop:
> > it appears to me that there's a failure in an attempt to recvmsg (EAGAIN)
> > (that might be the busy loop triger).
> > It's then followed by polling & reading the battery info.
> > Lots of the polls are non-blocking; I bet that's the cause.
> > 
> > Does the above make any sense?
> 
> The amount of polling doesn't look out of the ordinary. Your best bet is
> to install something like sysprof:
> https://git.gnome.org/browse/sysprof
> 
> (also available in distros)
> 
> and make sure that upower and its dependencies are either built with
> debug or have debuginfo packages installed.
> 
> This should point to where most of the time is spent.
> 
> It would be useful to reiterate which exact version of upower you're
> using, and maybe try a version of your distribution with upower 0.99.x
> if you're using an older version.
> 
> Cheers
> 
> _______________________________________________
> devkit-devel mailing list
> devkit-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/devkit-devel