After profiling upower, this is actually not an issue in there, as the only thing it is doing is getting the battery change event from the kernel, updating the internal struct and sending another dbus message so the clients could see the changes.
The main issue here is that the kernel is sending a big amount of battery events (all valid, and different changes), which results in udev, upower and dbus consuming a bit of your cpu. Verified this bug against both krillin and arale and that is not the case there, as I already did the profiling and reduced the amount of battery events. As this bug is just specific to mako, and would require a kernel change to reduce the amount of events, we can lower the priority and fix in vivid only. ** Summary changed: - upower consuming over 17% cpu + [mako] upower consuming over 17% cpu when in idle ** Description changed: From the meta battery bug # 1372413 mako running 191 As device was not suspending and battery level running down, upower is reported at 17%+ cpu by the cpustat tool - mpdecision and systemd-udevd also change their behavior. + mpdecision and systemd-udevd also change their behavior. + + The upower cpu consumption is just a side effect of the amount of + battery related events the kernel send, and specific to mako. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420395 Title: [mako] upower consuming over 17% cpu when in idle To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
