On 7/20/14 8:53 PM, Viral Wang wrote:
Hi David,
273mB memory setting in Flame only consider that we can have more memory from
the modem optimization.
We should also check the memory difference in display/camera.
One example is that we can gain 15-20mB more memory in homescreen in 2.0 if we
set display from FWVGA to HVGA.
(pmem/ION memory didn't count it)
zram will cost some physical memory and we should have a clear target before we
start to tune the zram.
We need to know the detail like pre-allocate memory, hw components and then we
can tune the parameters of zram.
Regards,
viral
I'm interested in seeing more details on how we can better simulate a
low end device with the Flame. We've been seeing a lot of MemShrink bugs
for 273MB devices where it looks like targeting higher end components
(primarily graphics) on a low memory device is most likely the root
cause of the issue, realistically these should be lower priority to fix
than real bugs that would show up on a 256MB device.
Viral suggests we set the display from FWVGA to HVGA. How is that
accomplished? Is that the correct approach?
Similarly how do we configure the zram? For this case it seems like
simply using a zram amount double that of tarako would be a simple naive
solution for the interim.
What I'd like to see come out of this is either a wiki page we can
reference for simulating a low end device with the Flame or just a
script that we can run from the B2G checkout.
-e
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
