Closed Bug 950976 Opened 11 years ago Closed 7 years ago

Evaluate how zram affects Nuwa

Categories

(Firefox OS Graveyard :: General, defect)

Unspecified
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: sinker, Unassigned)

References

Details

Once a process is swapped out by zram, it talks more time to bring them back.  The preallocated process of Nuwa is critical for the time of launching new apps.  We should evaluate how zram affects the launch time with Nuwa.
Currently I run on hamachi (production Alcatel One Touch Fire got from T-mobile Poland) with my own built kernel with enabled both zRAM and swapfile. b2g version is 1.4. Please contact with me if you need any help with the bug. I can perform some tests on it but don't know details.
Kai-Zhen, could you explain to mac how to get launch time of apps?


Basically, we want to see the launch time of apps when RSS and USS of the preallocated process are down to nearly 0 byte for zRAM's paging out.  So, you could open an app, membluster for example, to use as many memory as possible to force zram swapping out preallocated process.  Then, you could observe the change of launch time before and after swapping out of the preallocated process.
Flags: needinfo?(kli)
After enable "Time to load" in "setting->device information->more information->developer", launch time of each App will be displayed on right-top of screen.
Flags: needinfo?(kli)
Sure, but I need to know details. Are you guys available i.e. on Mozilla IRC #b2g ? What size of zRAM I should initialize?
Nuwa is gone after bug 1284674.
Status: NEW → RESOLVED
Closed: 7 years ago
OS: FreeBSD → Gonk (Firefox OS)
Hardware: x86 → Unspecified
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.