Closed
Bug 1483551
Opened 7 years ago
Closed 7 years ago
Resource starvation seems to affect WebRender more
Categories
(Core :: Graphics: WebRender, enhancement, P3)
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox63 | --- | affected |
People
(Reporter: jrmuizel, Unassigned)
References
Details
We should investigate how WebRender performs when a machine is under load.
Using the Quantum reference device or something like it (2C/4T) with an integrated GPU.
- See how WebRender performs with a program running in the background using 1,2 and 4 cores at 100%
- See how WebRender performs with a program using as much memory bandwidth as possible in the background.
- See how WebRender performs with a program trying to hog GPU resources.
| Reporter | ||
Updated•7 years ago
|
Blocks: wr-investigate
| Reporter | ||
Updated•7 years ago
|
Priority: -- → P2
Comment 1•7 years ago
|
||
I investigated this a little bit, using a quick-and-dirty load generator [1]. I simulated both CPU spin and CPU spin + memory traffic. I didn't simulate the GPU part, because that's harder and probably a lot less common.
My testing was pretty minimal (can do more later), but in general thinks look ok for WebRender. The resize experience is worse (bug 1486958) but some things were noticeably better, including scrolling on the w3c HTML spec.
I didn't test anything with high hard-disk usage, which is probably something that anti-virus does.
[1] https://jsfiddle.net/159pokym/25/
Updated•7 years ago
|
Blocks: stage-wr-trains
Updated•7 years ago
|
Priority: P2 → P3
| Reporter | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•