#8765 NORM Opportu: Clock activity hogs CPU.

[Zarro Boogs per Child]

#8765: Clock activity hogs CPU.
------------------------------+---------------------------------------------
   Reporter:  thomaswamm      |       Owner:  pierre       
       Type:  enhancement     |      Status:  new          
   Priority:  normal          |   Milestone:  Opportunity  
  Component:  clock-activity  |     Version:  not specified
 Resolution:                  |    Keywords:  clock        
Next_action:  diagnose        |    Verified:  0            
  Blockedby:                  |    Blocking:               
------------------------------+---------------------------------------------

Comment(by pierre):

 OK, the confusion come from the two different activities:
 * the clock-activity, which is the pippy one written by C Scott Ananian,
 which is in version 1 and hosted on
 http://dev.laptop.org/git?p=users/cscott/clock-activity-tmp;a=summary.
 * and the Clock activity I wrote, which is presently in version 3 and
 hosted on http://wiki.laptop.org/go/Clock_activity.

 Mine is not really CPU optimized at the moment. Though I read the SVG file
 only when needed (start, screen rotation or user displaying time) and
 cache it in a Pixbuf, I've noticed that X could consume 60% of the CPU
 when the clock is running, on the paint() call.

 I'll try to optimize mine with the technics you cite, disabling the timer
 when the clock is not visible. I'll study the code of the clock-activity-
 tmp so that my activity will be a better Sugar citizen.

-- 
Ticket URL: <http://dev.laptop.org/ticket/8765#comment:6>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system