With the recent testing of the Flame in a 273MB configuration we're
seeing a lot of bugs (like 1038938 and 1037383) where apps slow to a
crawl. It seems to me that we're are running with so little memory that
we're seeing old-time thrashing on the zmem swap partition.
So first of all: has anyone actually worked to tune the zmem parameters
in our builds? The Flame uses a 192mb zmem partition (see this line in
/init.target.rc |write /sys/block/zram0/disksize 192M|) If that is an
appropriate value for a 512 or 1024mb Flame, I wonder if it is actually
the best value for a 273mb flame. Maybe we would get better performance
if we had more uncompressed ram available for live apps?
And second: no matter how well we tune zram, if we've got zram swapping
turned on there are going to be low memory conditions where we are
swapping and the user sees apps running really slowly. I think we need
a FirefoxOS equivalent of the MacOS beachball.... Is there anyway we
can have something in gonk that detects swapping and draw something
directly to the screen (bypassing gecko and the system app) to let the
user know that the system is busy?
David
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
