On Wed, Aug 19, 2009 at 6:20 AM, Joel Stanleyj...@jms.id.au wrote:
When I first got Chromium going on the beagleboard it was slow. I
believe the the main slowdown is due to the limited RAM (128MB), but
another factor was the slow disk I/O due to the root fs being held on
a cheap SD card.
On Wed, Aug 19, 2009 at 19:38, Ben Laurieb...@chromium.org wrote:
warm: t= 397 528 3072 599
cold: t= 371 375 401 16
The cold startup are skewed as I suspect FUSE has extra caching that
/proc/sys/vm/drop_caches does not control. The warm startup numbers
show a
On Wed, Aug 19, 2009 at 5:09 AM, Joel Stanleyj...@jms.id.au wrote:
The 'cold' run calls fdatasync() then posix_fadvise() with
POSIX_FADV_DONTNEED on the binary before running the test. This is
appears to be the only difference between cold and warm. I'm running
2.6.31-rc6 from Ubuntu
On Wed, Aug 19, 2009 at 22:15, Evan Martine...@chromium.org wrote:
Just to eliminate any doubt, you can manually as root
echo 3 /proc/sys/vm/drop_caches
to force the caches to be dropped.
I have been doing this.
I don't know how slow I'd expect an SD card to be, but this random
page I
