On 26/10/08 14:21 -0400, Erik Garrison wrote:
On Fri, Oct 24, 2008 at 6:36 PM, Jordan Crouse [EMAIL PROTECTED] wrote:
On 25/10/08 00:00 +0200, NoiseEHC wrote:
The Geode X drive copyes every bit of data to the command ring buffer by
using the CPU so that is sure that those almost no CPU
On Fri, Oct 24, 2008 at 9:13 PM, Mitch Bradley [EMAIL PROTECTED] wrote:
Michael Stone wrote:
I did some basic profiling of my new rainbow code last night and
discovered that, in the best case with the current codebase on XO, it
costs about 0.5s/1 exec(python). Approximately 80% of the 0.5s was
Tomeu Vizoso wrote:
On Fri, Oct 24, 2008 at 9:13 PM, Mitch Bradley [EMAIL PROTECTED] wrote:
Michael Stone wrote:
I did some basic profiling of my new rainbow code last night and
discovered that, in the best case with the current codebase on XO, it
costs about 0.5s/1 exec(python).
On Fri, Oct 24, 2008 at 6:36 PM, Jordan Crouse [EMAIL PROTECTED] wrote:
On 25/10/08 00:00 +0200, NoiseEHC wrote:
The Geode X drive copyes every bit of data to the command ring buffer by
using the CPU so that is sure that those almost no CPU cycles thing is
at least a bit stretch... :)
For want it is worth, the team at the ministry of education in Peru
said that 8.2 feels faster to them. The aggregate user perception
vector is pointing in the right direction.
-walter
On Fri, Oct 24, 2008 at 1:58 PM, Tomeu Vizoso [EMAIL PROTECTED] wrote:
On Fri, Oct 24, 2008 at 7:04 PM,
On Fri, Oct 24, 2008 at 2:05 AM, Marco Pesenti Gritti
[EMAIL PROTECTED] wrote:
On Fri, Oct 24, 2008 at 1:56 AM, Marco Pesenti Gritti
[EMAIL PROTECTED] wrote:
* Activity startup is ridiculously slow.
Design an API incompatible Activity class. Start from a very basic
window and add
Marco,
I did some basic profiling of my new rainbow code last night and
discovered that, in the best case with the current codebase on XO, it
costs about 0.5s/1 exec(python). Approximately 80% of the 0.5s was
spent importing modules.
I hope to dig deeper in the near future, but I am concerned at
On Fri, Oct 24, 2008 at 10:10 PM, Michael Stone [EMAIL PROTECTED] wrote:
Marco,
I did some basic profiling of my new rainbow code last night and
discovered that, in the best case with the current codebase on XO, it
costs about 0.5s/1 exec(python). Approximately 80% of the 0.5s was
spent
On Fri, 24 Oct 2008, Michael Stone wrote:
Marco,
I did some basic profiling of my new rainbow code last night and
discovered that, in the best case with the current codebase on XO, it
costs about 0.5s/1 exec(python). Approximately 80% of the 0.5s was
spent importing modules.
a silly
On Fri, Oct 24, 2008 at 7:04 PM, Sayamindu Dasgupta [EMAIL PROTECTED] wrote:
On Fri, Oct 24, 2008 at 10:10 PM, Michael Stone [EMAIL PROTECTED] wrote:
Marco,
I did some basic profiling of my new rainbow code last night and
discovered that, in the best case with the current codebase on XO, it
Michael Stone wrote:
I did some basic profiling of my new rainbow code last night and
discovered that, in the best case with the current codebase on XO, it
costs about 0.5s/1 exec(python). Approximately 80% of the 0.5s was
spent importing modules.
I hope to dig deeper in the near future, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Erik Garrison wrote:
What about changing the kind of visual feedback we give. Instead of
pulsing icons what about icons with a string of dots beneath, a progress
bar, flashing, or another kind of overlay feedback which requires fewer
visual
The Geode X drive copyes every bit of data to the command ring buffer by
using the CPU so that is sure that those almost no CPU cycles thing is
at least a bit stretch... :) According to Jordan Crouse it will not be
better but he was not too concrete so in the end I am not sure what he
was
On 25/10/08 00:00 +0200, NoiseEHC wrote:
The Geode X drive copyes every bit of data to the command ring buffer by
using the CPU so that is sure that those almost no CPU cycles thing is
at least a bit stretch... :) According to Jordan Crouse it will not be
better but he was not too concrete
Could you be a bit more specific, please? What did you mean when you
talked about that moving a little bit more of the driver to kernel level
would not help? (This was the mentioned thread I had with Bernie.)
Also could somebody enlighten me why we does not use DirectFB? Is it
because of there
On 25/10/08 00:48 +0200, NoiseEHC wrote:
Could you be a bit more specific, please? What did you mean when you
talked about that moving a little bit more of the driver to kernel level
would not help? (This was the mentioned thread I had with Bernie.)
I'm not exactly which part you want more
Problems and ideas in no particular order.
* Sugar shell startup is too slow.
Reduce dependencies, single process shell, modularize and delay
initialization of components which are not immediately necessary,
measure constantly to avoid regressions and monitor progress.
* Icons rendering is slow
On Fri, Oct 24, 2008 at 1:56 AM, Marco Pesenti Gritti
[EMAIL PROTECTED] wrote:
* Activity startup is ridiculously slow.
Design an API incompatible Activity class. Start from a very basic
window and add functionalities on the top of it, trying to not regress
startup time. Make sure that
18 matches
Mail list logo
