On Wed, Sep 15, 2010 at 00:46, Sugar Labs Bugs
bugtracker-nore...@sugarlabs.org wrote:
#2141: Memory and CPU status indicator for the frame.
--+-
Reporter: m_anish | Owner: tomeu
On Wed, Sep 15, 2010 at 00:46, Sugar Labs Bugs
bugtracker-nore...@sugarlabs.org wrote:
#2141: Memory and CPU status indicator for the frame.
--+-
Reporter: m_anish | Owner: tomeu
On Wed, Sep 15, 2010 at 10:40:06AM +0200, Tomeu Vizoso wrote:
Basically, I don't see how this could work without being tuned to very
specific systems.
I've reviewed the patch [1], and I disagree with your assessment. It
would work without any tuning to specific systems. The learner would
On Wed, Sep 15, 2010 at 12:12, James Cameron qu...@laptop.org wrote:
On Wed, Sep 15, 2010 at 10:40:06AM +0200, Tomeu Vizoso wrote:
Basically, I don't see how this could work without being tuned to very
specific systems.
I've reviewed the patch [1], and I disagree with your assessment. It
On Wed, Sep 15, 2010 at 5:59 AM, Tomeu Vizoso to...@sugarlabs.org wrote:
On Wed, Sep 15, 2010 at 12:12, James Cameron qu...@laptop.org wrote:
On Wed, Sep 15, 2010 at 10:40:06AM +0200, Tomeu Vizoso wrote:
Basically, I don't see how this could work without being tuned to very
specific systems.
There is information in the /proc filesystem we could use to refine
the heuristics.
/proc/meminfo - How much physical memory.
/proc/loadavg - How many IOWAIT cycles.
/proc/cpuinfo - How fast is my machine. How many CPUs.
But I guess we should try out the current resource indicator on many
On Wed, Sep 15, 2010 at 16:46, Sascha Silbe
sascha-ml-reply-to-201...@silbe.org wrote:
Excerpts from Tomeu Vizoso's message of Wed Sep 15 10:40:06 +0200 2010:
Basically, I don't see how this could work without being tuned to very
specific systems.
I still don't see how it is tuned to
On 09/15/2010 10:48 AM, Anish Mangal wrote:
Here's how it works.
0 memory free 100
0 cpu free 100
0 mem + cpu free = 67= unhappy
67 mem + cpu free = 133 = serious/normal
133 mem + cpu free = 200 = happy
I don't think this is a good enough heuristic.
1. CPU
On Wed, Sep 15, 2010 at 11:36 AM, Benjamin M. Schwartz
bmsch...@fas.harvard.edu wrote:
I don't think this is a good enough heuristic.
Agreed -- that's a terrible heuristic. And happy/sad face is a
terrible UI. The computer is not happy or sad; it's _working_.
Honestly, there is a base problem
On 16 September 2010 03:53, Martin Langhoff martin.langh...@gmail.comwrote:
Agreed -- that's a terrible heuristic. And happy/sad face is a
terrible UI. The computer is not happy or sad; it's _working_.
I recently learned that when an autistic child played a Gcompris game on
Sugar and were
On 16 September 2010 09:24, Tabitha Roder tabi...@tabitha.net.nz wrote:
When I was in Samoa at their olpc deployment, I found the kids started lots
of activities but no one had told them how to stop an activity. I tried to
explain why the XOs were not responsive by saying that the computer was
On Sun, Aug 29, 2010 at 02:57, Sugar Labs Bugs
bugtracker-nore...@sugarlabs.org wrote:
#2141: Memory and CPU status indicator for the frame.
--+-
Reporter: m_anish | Owner: tomeu
12 matches
Mail list logo
