951601 - Disable memory-pressure temporary for launching new content processes.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[Thinker Li [:sinker]]

It is very common to eat out system memory at first few seconds of a new content process.  It usually trigger memory-pressure before low-memory killer.  Low memory pressure would wake up GC of existing content processes, it would slow down the new process.  Maybe, we should kill processes instead of memory-pressure to improve launch time of apps.

The idea is to disable/ignore memory-pressure events at first few seconds (2s?) to let OOM work for us.  Maybe, we should restart to handle memory-pressure events after first OOM of launching a new content process.

Comment 1

[ying.xu]

// Fire a memory pressure event when the system has less than Xmb of memory
// remaining.  You should probably set this just above Y.KillUnderMB for
// the highest priority class Y that you want to make an effort to keep alive.
// (For example, we want BACKGROUND_PERCEIVABLE to stay alive.)  If you set
// this too high, then we'll send out a memory pressure event every Z seconds
// (see below), even while we have processes that we would happily kill in
// order to free up memory.
pref("hal.processPriorityManager.gonk.notifyLowMemUnderMB", 14);

I think changing the value of hal.processPriorityManager.gonk.notifyLowMemUnderMB could achieve your goal.

Comment 2

[thomas tsai]

notifyLowMemUnderMB to 15MB which won't hit the low memory after boot up (free memory is bigger than 16MB now)
and GC by memory pressure lower to 10MB which won't start GC too early.

Comment 3

[Joe Cheng [:jcheng] (please needinfo)]

hi patrick, it is believed this is a dup to a bug you are working on. Can you please confirm? thanks

Comment 4

[Patrick Wang (Chih-Kai Wang) (:kk1fff)]

I think so.

Comment 5

[BMO Automation]

Firefox OS is not being worked on