Open Bug 1416082 (motionmark) Opened 7 years ago Updated 3 months ago

[meta] MotionMark perf

Categories

(Core :: Graphics, defect, P3)

defect

Tracking

()

Tracking Status
firefox57 --- unaffected
firefox58 --- unaffected

People

(Reporter: jrmuizel, Unassigned)

References

(Depends on 8 open bugs, Blocks 1 open bug, )

Details

(Keywords: meta)

      No description provided.
Depends on: 1416073, 1416076
Depends on: 1401672
Depends on: 1415407
Depends on: 1415586
Keywords: meta
Alias: motionmark-meta
Depends on: 1417614
Depends on: 1417616
Depends on: 1417621
Depends on: 1417622
Depends on: 1417624
Depends on: 1419863
Depends on: 1419871
Depends on: 1419876
Depends on: 1419882
Depends on: 1419891
I filed https://github.com/servo/webrender/issues/2087 to WR which has some extra sub-issues not (yet) reflected here.
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
Depends on: 1421054
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".
That's really surprising. I filed bug 1453991 about it.
(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
Bug 1371668 might cause the regression of Comment 5.
(In reply to Sotaro Ikeda [:sotaro] from comment #6)
> Bug 1371668 might cause the regression of Comment 5.

Bug 1462503 is related bug.
See Also: → 1462503
Priority: -- → P3
This is a meta, so no priority needed
Priority: P3 → --

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.

Component: Graphics: WebRender → Graphics
Depends on: 1553571, 1553575
Depends on: 1566829
Depends on: 1566826
Priority: -- → P3
Depends on: 1582621
Alias: motionmark-meta → motionmark
Severity: normal → S3
Depends on: 1795768
Depends on: 1800977
Depends on: 1805056
Depends on: 1848050
Depends on: 1795511
Depends on: 1857094
Depends on: 1879178
You need to log in before you can comment on or make changes to this bug.