Firefox doesn't seem use 'above normal' priority for GPU process on Windows like some other browsers
Categories
(Core :: Graphics, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox147 | --- | fixed |
People
(Reporter: smaug, Assigned: bradwerth)
References
Details
Attachments
(3 files)
I was testing a new Intel 268v based Windows 11 laptop and scrolling feels a bit jank-y when using it on battery. Based on Task Manager Edge uses 'above normal' priority for couple of processes, I assume one of those is their GPU process. FF doesn't.
When tweaking FF's GPU process priority manually using Task Manager, scrolling/panning becomes very smooth.
Bug 1671490 was supposed to fix this, but at least I don't see it working.
Comment 1•7 months ago
|
||
A profile would help, we have markers showing the priorities (both requested, and actual priorities).
| Reporter | ||
Comment 2•7 months ago
|
||
https://share.firefox.dev/45D5WXO
And with high prio gpu process https://share.firefox.dev/3Vq4bal
| Reporter | ||
Updated•7 months ago
|
Comment 3•7 months ago
|
||
The Performance Impact Calculator has determined this bug's performance impact to be medium. If you'd like to request re-triage, you can reset the Performance Impact flag to "?" or needinfo the triage sheriff.
Platforms: Windows
Impact on browser: Causes noticeable jank
[x] Able to reproduce locally
Comment 4•6 months ago
|
||
The severity field is not set for this bug.
:bhood, could you have a look please?
For more information, please visit BugBot documentation.
Comment 5•6 months ago
|
||
(In reply to Olli Pettay [:smaug][bugs@pettay.fi] from comment #2)
Thanks for the profiles. The patch from bug 1671490 seems to behave as expected in this profile. The parent process main thread and the GPU process main thread have the same priorities (before the patch the GPU process had a lower priority because it didn't have any visible window). The GPU process Rendered thread priority is slightly higher, and the content process priorities are slightly lower.
And with high prio gpu process https://share.firefox.dev/3Vq4bal
In this profile the priority of the entire GPU process is very high, close to the maximum.
Updated•6 months ago
|
| Reporter | ||
Comment 6•6 months ago
|
||
Based on the Windows profile manager GPU process had normal priority.
And anyhow, FF behavior is pretty bad with the current setup.
Comment 7•6 months ago
|
||
Dropping into triage for the team to evaluate this week.
Updated•6 months ago
|
Comment 8•6 months ago
|
||
Discussed this with Bob briefly - we should definitely make sure we do what's needed to ensure the main GPU process threads don't get scheduled on e-cores. I don't know exactly what the win apis are to do this, but I imagine it's fairly straightforward.
| Assignee | ||
Comment 9•6 months ago
|
||
I think I'll be able to improve behavior here.
Updated•6 months ago
|
| Assignee | ||
Comment 10•4 months ago
|
||
This one-time sets the priority of the gpu process, which should have a
lasting effect, because it's not set anywhere else.
| Assignee | ||
Comment 11•4 months ago
|
||
| Assignee | ||
Comment 12•4 months ago
|
||
Comment 13•4 months ago
|
||
Comment 14•4 months ago
|
||
Comment 15•4 months ago
|
||
Backed out for causing build bustages @LinuxProcessPriority.cpp.
Comment 16•4 months ago
|
||
Comment 17•4 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/e0147286c6fd
https://hg.mozilla.org/mozilla-central/rev/d49a066f2459
https://hg.mozilla.org/mozilla-central/rev/33bfa51fd872
| Assignee | ||
Updated•4 months ago
|
Updated•3 months ago
|
Description
•