Closed Bug 762782 Opened 12 years ago Closed 12 years ago

See if dom.ipc.content.nice makes a difference for content processes in gonk

Categories

(Firefox OS Graveyard :: General, defect)

Product:
Firefox OS Graveyard
Component:
General
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-kilimanjaro:?, blocking-basecamp:-)

Status:
RESOLVED DUPLICATE of bug 780437
Project Flags:
blocking-kilimanjaro ?
blocking-basecamp -

People

(Reporter: cjones, Unassigned)

References

Details

We added this way back when, for xul-fennec.  It improved responsiveness quantitatively on single-core devices.  Dropping prio on content processes made sense in xul-fennec, because the chrome process consumed significant CPU in the steady state (CPU compositing) so the two would compete.

In b2g, our master process should be mostly idle, and the newer linux schedulers should be friendly to it.  But nice'ing up the content process might help a little.

Can experiment by changing the pref dom.ipc.content.nice or setting MOZ_CHILD_PROCESS_RELATIVE_NICENESS.
blocking-basecamp: --- → ?
blocking-kilimanjaro: --- → ?
blocking-basecamp: ? → -
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.