Closed
Bug 1410851
Opened 8 years ago
Closed 3 years ago
MazeSolver suddenly extremely slow with WebRender
Categories
(Core :: Graphics: WebRender, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| firefox57 | --- | unaffected |
| firefox58 | --- | unaffected |
People
(Reporter: niels.breuker, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: regression, regressionwindow-wanted, Whiteboard: [wr-reserve][gfx-noted])
Attachments
(1 file)
|
309.83 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
Build ID: 20171022220103
Steps to reproduce:
I tested WebRender on MazeSolver a few weeks ago and again today.
To try this yourself:
1. Enable WebRender on Nightly with gfx.webrender.enabled, gfx.webrendest.enabled and gfx.webrender.blob-images set to true.
2. Go to https://testdrive-archive.azurewebsites.net/Performance/MazeSolver/Default.html
3. Open console and call 'changeMazeSize(51)'
4. Press start
The reason I change the size to 51 is because it's a pretty big maze and the browser has to go through almost everything in order to go to the end.
Actual results:
WebRender was incredibly slow suddenly
Expected results:
I expected the results to be similar or better than a few weeks ago.
WebRender used to be extremely fast on MazeSolver. A maze with the size of 51 was done in 25 seconds. No other engine could match that.
Updated•8 years ago
|
Component: Untriaged → Graphics: WebRender
Product: Firefox → Core
Comment 1•8 years ago
|
||
Can you use mozregression to track down a regression range?
Keywords: regression,
regressionwindow-wanted
Updated•8 years ago
|
Whiteboard: [wr-mvp] [triage]
How's this related to bug 1395184?
See Also: → 1395184
Updated•8 years ago
|
Blocks: stage-wr-next
status-firefox57:
--- → unaffected
status-firefox58:
--- → unaffected
Priority: -- → P3
Updated•8 years ago
|
Whiteboard: [wr-mvp] [triage] → [wr-reserve]
Updated•8 years ago
|
Whiteboard: [wr-reserve] → [wr-reserve][gfx-noted]
Comment 3•8 years ago
|
||
Is this bug still valid? I just ran the test with webrender and it is faster than the current release version.
| Reporter | ||
Comment 4•8 years ago
|
||
It's much faster again, but it's still not at the level it was a few months ago. Currently a maze with the size of 51 is done in 48 seconds with WebRender on while a few months back it was done in 25 seconds. https://bug1410851.bmoattachments.org/attachment.cgi?id=8921020
Updated•8 years ago
|
Blocks: webrender-site-issues
| Reporter | ||
Comment 5•8 years ago
|
||
MazeSolver on my integrated GPU (Intel HD 630) is equally fast with my discrete GPU (NVIDIA GeForce 960M), so I doubt the bottleneck is in GPU side of WebRender.
A lot of time is spent in Retained Display List update and serializing WR commands on this test.
Comment 7•3 years ago
|
||
Seems to run well on the couple machines I tested on recently.
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•