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

Sugar Labs Bugs bugtracker-noreply at sugarlabs.org
Sat Aug 21 12:10:18 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                

Comment(by sascha_silbe):

 Replying to [comment:8 tomeu]:

 > 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.

 The combined display ("mood") might not work too well on systems with lots
 of RAM, but other than that I fail to see why the proposed device icon
 would fail to be useful on a wide range of systems. Even for single-user
 systems the resource usage isn't entirely up to the user to control (e.g.
 cron jobs); but that doesn't imply it doesn't matter to know about current
 resource usage.
 The palette shows cumulative resource usage as a fraction, so there's no
 dependency on particular hardware specs like memory size, number of CPUs
 or CPU frequency.

 > 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.

 Another important measure is IO-wait. IIRC the CPU calculation was chosen
 to reflect this, so the CPU part shouldn't be dropped.

 > 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.

 I have to disagree. On all systems I've used so far, knowing about current
 resource usage is important. I use top about once a day on average,
 including on my dual-core, 1.9GHz workstation with 4GB of RAM.

 > 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.

 If you don't want this to be enabled by default, please at least ship it
 in a "contrib" directory so enabling it is as easy as creating a symlink.
 The clock device icon could ship in the same directory then. It's the #1
 reason I bring up the Frame (#2 is wifi status).

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

More information about the Bugs mailing list