Closed Bug 1548364 Opened 5 years ago Closed 5 years ago

Enable dom.ipc.processPriorityManager.enabled by default on Windows


(Core :: DOM: Content Processes, enhancement)

Not set



Tracking Status
relnote-firefox --- 69+
firefox69 --- fixed


(Reporter: mconley, Assigned: mconley)


(Blocks 1 open bug)



(1 file)

The report in bug 1532767 shows that, according to our Beta experiment, the process priority manager had no measurable impact on page load time, tab switch time, or user retention.

So, the good news is that it doesn't appear to make things worse. However, I'm a bit sad to say that it also didn't appear to make things better (via the probes that we measure).

We do know, however, that lowering background tab process priority allows the OS to prioritize work in foreground tabs. So at the very least, this should be a resource usage win.

So I think we should go ahead and enable this and let it ride out.

Type: defect → enhancement

esmyth signed off on letting this ride the trains in Slack.

Release Note Request (optional, but appreciated)
[Why is this notable]:
This enables a component that allows Firefox to give Windows hints on how best to prioritize CPU usage. Specifically, content processes that only host tabs that are in the background will have their priorities lowered so that foreground processes can get more processor time if they need it.

[Suggested wording]:
Firefox will give Windows hints to appropriately set content process priority levels, meaning more processor time spent on the tasks you're actively working on, and less processor time spent on things in the background (with the exception of video and audio playback).

relnote-firefox: --- → ?
Pushed by
Let the Process Priority Manager ride out to the release channel on Windows. r=gsvelto
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69

Added to the Fx69 Beta release notes.

You need to log in before you can comment on or make changes to this bug.