Closed
Bug 1419353
Opened 7 years ago
Closed 6 years ago
No better than 30fps on low end surface tablet
Categories
(Core :: Graphics: WebRender, defect, P4)
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox57 | --- | unaffected |
| firefox59 | --- | affected |
People
(Reporter: nical, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [gfx-noted])
I tried WebRender on a windows 10 surface tablet equipped with an intel atom x7-z8700 CPU @ 1.6Ghz 2Go RAM GPU id 0x22b0 version 20.19.15.4424.
At best we get 30 fps on all of the pages that I tried including simple ones, with a lot of time (30ms+) attributed to the compositor according to webrender's built-in profiling ui (render backend stays around a reasonable ~3ms). I suppose that a lot of this time is actually spent waiting for the GPU but the gpu profile markers aren't enabled in gecko yet, I'll look again when they are hooked up.
Without WebRender, Firefox runs very smoothly on this device.
|
Reporter | |
Comment 1•7 years ago
|
||
WebRender issue: https://github.com/servo/webrender/issues/2071
|
||
Updated•7 years ago
|
|
||
Updated•7 years ago
|
Whiteboard: [gfx-noted][wr-mvp] [triage] → [gfx-noted]
|
||
Comment 2•7 years ago
|
||
This seems related to https://bugzilla.mozilla.org/show_bug.cgi?id=1417633
Perhaps WebRender in Gecko gets really slow as the speed of the CPU decreases.
|
||
Comment 3•6 years ago
|
||
Bug 1500017 might be related.
|
|
||
Updated•6 years ago
|
OS: Unspecified → Windows 10
|
|
Reporter | |
Comment 5•6 years ago
|
||
I just tried on the same surface tablet and the performance is good.
Interestingly, enabling gpu sample queries or gpu time queries make the compositor CPU time go from 5ms to 35ms per frame.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(nical.bugzilla)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•