#2997 NORM Untriag: Unexpected Journal memory footprint behavior

[Zarro Boogs per Child]

#2997: Unexpected Journal memory footprint behavior
-------------------------------+--------------------------------------------
  Reporter:  lincolnquirk      |       Owner:  tomeu    
      Type:  defect            |      Status:  closed   
  Priority:  normal            |   Milestone:  Untriaged
 Component:  journal-activity  |     Version:           
Resolution:  duplicate         |    Keywords:           
  Verified:  0                 |  
-------------------------------+--------------------------------------------
Changes (by danw):

  * status:  new => closed
  * resolution:  => duplicate

Comment:

 Yeah, see #2030, especially http://dev.laptop.org/ticket/2030#comment:22
 and http://dev.laptop.org/ticket/2030#comment:24. As Hello1024 noted, most
 of the memory footprint changes you're seeing are just artifacts of the
 current not-so-great algorithm, but it will be better soon.

 The activity ring is not intended for low-level memory debugging though;
 use memphis in the developer console for that.

-- 
Ticket URL: <https://dev.laptop.org/ticket/2997#comment:3>
One Laptop Per Child <http://laptop.org/>