Status
()
People
(Reporter: jrmuizel, Assigned: jrmuizel)
Tracking
(Depends on: 1 bug)
Firefox Tracking Flags
(firefox67 fixed)
Details
Attachments
(1 attachment)
Comment hidden (empty) |
(Assignee) | ||
Comment 1•21 days ago
|
||
Created attachment 9040464 [details]
Bug 1524284. Enable WebRender by default on modern Intel desktop gpus.
This enables WebRender on a small subset of modern Intel gpus.
Comment 2•21 days ago
|
||
I think you will see a lot of crashes due to Bug 1479795. I used to hit that crash way more easily with WR than without it.
Newer drivers work perfectly, but the one pushed by Windows Update is bugged.
Pushed by jmuizelaar@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7998879d6713 Enable WebRender by default on modern Intel desktop gpus. r=kats
Updated•21 days ago
|
Comment 4•21 days ago
|
||
bugherder |
Comment 5•16 days ago
|
||
What are "modern intel desktop GPUs"?
I had a not-that-great experience running WR enabled on Intel Skylake (HD 520) on both - Windows and Linux on a 4K display.
Rendering was pixel-perfect, performance however was not that gread - Firefox felt somehow sluggish on many pages.
So no hard numbers, just a "feel" - maybe pushing 4k pixels at each redraw is a bit tough for those GPUs (this makes me wonder how WR will perform efficiency-wise on battery-powered devices - memory bandwidth is quite costly energy-wise).
(Assignee) | ||
Comment 6•16 days ago
|
||
(In reply to Clemens Eisserer from comment #5)
What are "modern intel desktop GPUs"?
Right now that means Skylake and newer. Very shortly it will be Haswell and newer.
I had a not-that-great experience running WR enabled on Intel Skylake (HD 520) on both - Windows and Linux on a 4K display.
Rendering was pixel-perfect, performance however was not that gread - Firefox felt somehow sluggish on many pages.
So no hard numbers, just a "feel" - maybe pushing 4k pixels at each redraw is a bit tough for those GPUs (this makes me wonder how WR will perform efficiency-wise on battery-powered devices - memory bandwidth is quite costly energy-wise).
Is your experience recent? i.e have you tried since picture caching was enabled? If so can file bugs for any pages you encounter this today?