[Bugs] #2141 UNSP: Memory and CPU status indicator for the frame.

Sugar Labs Bugs bugtracker-noreply at sugarlabs.org
Sun Aug 15 11:56:39 EDT 2010

#2141: Memory and CPU status indicator for the frame.
    Reporter:  m_anish                    |          Owner:  tomeu                      
        Type:  enhancement                |         Status:  new                        
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  sugar                      |        Version:  Unspecified                
    Severity:  Unspecified                |       Keywords:  r! dextrose                
Distribution:  Unspecified                |   Status_field:  Unconfirmed                
Changes (by tomeu):

  * keywords:  r? dextrose => r! dextrose


 Have given it a go in my machine and have been thinking a bit about it,
 and I'm quite unsure we can find a set of parameters that work well in all
 the scenarios where Sugar is expected to run. Consider for example a LTSP
 environment where all the Sugar instances share the same address space.

 I'm also concerned that we are going to pay a penalty for updating the CPU
 usage when we agreed that the important measure is memory.

 There has been some discussion about this in #sugar involving Daniel and
 Bernie, Anish, have you read it?

 I think work like this belongs better outside the sugar source tree until
 we agree this is of general interest to all the users we are targeting. I
 know XOs are our most important use base by large, but we still aim to
 grow to other areas. Extensions exist precisely so people can extend the
 Sugar shell without having to either patch or go through all the
 submission process, I don't think we should try to upstream everything.

Ticket URL: <http://bugs.sugarlabs.org/ticket/2141#comment:8>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system

More information about the Bugs mailing list