Open
Bug 1416082
(motionmark)
Opened 7 years ago
Updated 1 year ago
[meta] MotionMark perf
Categories
(Core :: Graphics, defect, P3)
Core
Graphics
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox57 | --- | unaffected |
firefox58 | --- | unaffected |
People
(Reporter: jrmuizel, Unassigned)
References
(Depends on 9 open bugs, Blocks 2 open bugs, )
Details
(Keywords: meta)
No description provided.
Reporter | ||
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Reporter | ||
Updated•7 years ago
|
Alias: motionmark-meta
Comment 1•7 years ago
|
||
I filed https://github.com/servo/webrender/issues/2087 to WR which has some extra sub-issues not (yet) reflected here.
Comment 2•7 years ago
|
||
I dug up the last time [1] I had to investigate a MotionMark/Animometer perf slowdown; some of the analysis there might be obsolete but it might be helpful to understand how the test is non-linear and what are some settings you can fiddle with to make it behave more linearly in order to optimize it without getting super-noisy results. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1276713
Comment 3•7 years ago
|
||
Today, I checked MotionMark score on my Win10 PC(P50). I was surprised that the score of "WebRender without DirectComposition" was too low. I disabled DirectComposition by "gfx.webrender.dcomp-win.enabled;false". - Firefox nightly(CompositorD3D 11): 90-100 - Firefox nightly(WebRender with DirectComposition): 145-160 - Firefox nightly(WebRender without DirectComposition):6-12 By the way, the scores became better with "Windows 10 Spring Creators Update".
Reporter | ||
Comment 4•7 years ago
|
||
That's really surprising. I filed bug 1453991 about it.
Comment 5•6 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #3) > Today, I checked MotionMark score on my Win10 PC(P50). I was surprised that > the score of "WebRender without DirectComposition" was too low. I disabled > DirectComposition by "gfx.webrender.dcomp-win.enabled;false". > > - Firefox nightly(CompositorD3D 11): 90-100 > - Firefox nightly(WebRender with DirectComposition): 145-160 > - Firefox nightly(WebRender without DirectComposition):6-12 > > By the way, the scores became better with "Windows 10 Spring Creators > Update". Motion mark score was regressed a lot recently on nightly. On latest nightly, the score was like the following. - Firefox nightly(Direct3D 11 (Advanced Layers)): 70-80 - Firefox nightly(WebRender with DirectComposition): 90-110
Comment 6•6 years ago
|
||
Bug 1371668 might cause the regression of Comment 5.
Comment 7•6 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #6) > Bug 1371668 might cause the regression of Comment 5. Bug 1462503 is related bug.
Updated•6 years ago
|
Updated•6 years ago
|
Priority: -- → P3
Comment 9•6 years ago
|
||
I tested with http://browserbench.org/MotionMark/. Recently score of MotionMark was improved a lot!
On my laptop(P50 Win10), the score was around 100-120, today, the score became 200-240. Chrome was 200-230.
Reporter | ||
Updated•5 years ago
|
Component: Graphics: WebRender → Graphics
Reporter | ||
Updated•5 years ago
|
Updated•5 years ago
|
Priority: -- → P3
Updated•5 years ago
|
Depends on: fission-motionmark
Updated•5 years ago
|
Blocks: wr-displaylist-perf
Reporter | ||
Updated•3 years ago
|
Alias: motionmark-meta → motionmark
Updated•2 years ago
|
Severity: normal → S3
Comment hidden (advocacy) |
Comment 11•2 years ago
|
||
Opened this for canvas https://bugzilla.mozilla.org/show_bug.cgi?id=1805056
You need to log in
before you can comment on or make changes to this bug.
Description
•