#3438 HIGH First D: Optimize drawing code and response time of Measure Activity

[Zarro Boogs per Child]

#3438: Optimize drawing code and response time of Measure Activity
-------------------------------+--------------------------------------------
  Reporter:  arjs              |       Owner:  bernie                                  
      Type:  enhancement       |      Status:  new                                     
  Priority:  high              |   Milestone:  First Deployment, V1.0                  
 Component:  measure-activity  |     Version:  Development build as of this date       
Resolution:                    |    Keywords:  optimize drawing, response time, measure
  Verified:  0                 |  
-------------------------------+--------------------------------------------
Changes (by tomeu):

 * cc: tomeu (added)


Comment:

 43% of total cpu time is spent in cairo.stroke() and 32% in cairo.paint().
 Those are C code, so I don't see how rewriting anything from python to C
 will help here (in the short/medium term). Also, those calls are more or
 less called the same number of times.

 The next thing I would do if I had to optimize this is to profile with
 something that can "see" inside cairo. That would be sysprof or oprofile.
 Look into the devel ml archives or in the wiki or ask in #olpc or #sugar
 if you need some pointers about it. You will need to install some
 debuginfo rpms to get meaningful results.

 Nevertheless that, if you find a way to call those methods less often and
 still get the desired results, go for it.

 If not, we should discover why cairo is being so slow, and a system level
 profile would tell.

-- 
Ticket URL: <https://dev.laptop.org/ticket/3438#comment:16>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system