#2030 NORM Trial-3: Activity wedge memory footprint representation

[Zarro Boogs per Child]

#2030: Activity wedge memory footprint representation
---------------------+------------------------------------------------------
  Reporter:  Eben    |       Owner:  danw   
      Type:  defect  |      Status:  new    
  Priority:  normal  |   Milestone:  Trial-3
 Component:  sugar   |     Version:         
Resolution:          |    Keywords:  review?
  Verified:  0       |  
---------------------+------------------------------------------------------
Changes (by danw):

 * cc: edsiper (added)
  * keywords:  => review?

Comment:

 Updated patch attached. It now uses /proc/PID/smaps as described in
 comment 22.

 marco/edsiper, what should we do about proc_smaps.py? Currently there
 doesn't seem to be anything shared between sugar/services/ and any other
 part of sugar. Is it ok to put it in sugar/sugar/ and have the console
 import it?

 The other big change in this version is that now, if the ring is visible,
 then we don't change the size of existing wedges when adding or removing
 an activity from it. This means that the ring will be a little bit off
 (because the memory assigned to various shared mappings needs to be
 reallocated between the different wedges), but this doesn't really matter
 because we'll eventually get a chance to redraw it when the user isn't
 looking.

-- 
Ticket URL: <http://dev.laptop.org/ticket/2030#comment:24>
One Laptop Per Child <http://laptop.org/>