dx-packages team mailing list archive

Thread
Date

[Bug 1221871] Re: indicator-power-service is a lightly busy all the time

To: dx-packages@xxxxxxxxxxxxxxxxxxx
From: Charles Kerr <charles.kerr@xxxxxxxxxxxxx>
Date: Thu, 13 Mar 2014 21:32:49 -0000
Reply-to: Bug 1221871 <1221871@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: indicator-power
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1221871

Title:
  indicator-power-service is a lightly busy all the time

Status in The Power Indicator:
  Fix Released
Status in “indicator-power” package in Ubuntu:
  Fix Released

Bug description:
  In a vain attempt to reduce power on these phone devices I noticed
  that indicator-power-service is using just under 1% of one CPU all the
  time.

   CPU usage:
    PID  Process                USR%   SYS%  TOTAL%
    1358 indicator-power-serv   0.05   0.04   0.08 (very light load)

  It seems to be waiting on poll() on a couple of threads which
  cumulatively add up to about 1.68 wakeups a second over a 1 hour
  analysis:

  Top polling system calls:

  PID     
    1369 indicator-power-serv poll                    1.3462 polls/sec
    1358 indicator-power-serv poll                    0.3376 polls/sec
   Total                                              1.6838 polls/sec

  This contributes to a bunch of context switching by these threads:

  Context Switches:
    PID  Process                Voluntary   Involuntary     Total
                               Ctxt Sw/Sec  Ctxt Sw/Sec  Ctxt Sw/Sec
    1369 indicator-power-serv        10.75         0.15        10.90 (moderate)
    1358 indicator-power-serv         3.53         0.07         3.60 (low)
    1372 indicator-power-serv         0.00         0.00         0.00 (idle)
   Total                             14.29         0.22        14.50

  [ See the attached log, launchpad formatting sucks ]

  I also observed a couple of brk() calls, and a small amount of heap
  growth which may indicate it has a small memory leak, but I am
  speculating on this.

  Attached is a full report from a 1 hour of monitoring indicator-power-
  service for reference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1221871/+subscriptions