Closed
Bug 1417621
Opened 7 years ago
Closed 7 years ago
[meta] MotionMark CSS bouncing filter circles runs slower than Nightly
Categories
(Core :: Graphics: WebRender, enhancement, P3)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox57 | --- | unaffected |
People
(Reporter: jrmuizel, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: meta, Whiteboard: [gfx-noted])
http://browserbench.org/MotionMark/developer.html?test-interval=30&display=minimal&tiles=big&controller=ramp&frame-rate=50&kalman-process-error=1&kalman-measurement-error=4&time-measurement=performance&suite-name=HTMLsuite&test-name=CSSbouncingfiltercircles&complexity=92
I get a score of 54.82 w/webrender vs 122 w/Nightly
Reporter | ||
Updated•7 years ago
|
Blocks: motionmark
Updated•7 years ago
|
Whiteboard: [wr-mvp] [triage]
Reporter | ||
Comment 1•7 years ago
|
||
We have a fallback extravaganza on this. Turning on paint-flashing reveals its greatness.
Reporter | ||
Comment 2•7 years ago
|
||
Here's the list of filters used:
'grayscale(50%)',
'sepia(50%)',
'saturate(50%)',
'hue-rotate(180)',
'invert(50%)',
'opacity(50%)',
'brightness(50%)',
'contrast(50%)',
'blur(10px)',
'drop-shadow(10px 10px 10px gray)'
with bug 1415407 we support them all except for drop-shadow
Depends on: 1415407
Updated•7 years ago
|
status-firefox57:
--- → unaffected
Priority: -- → P3
Whiteboard: [wr-mvp] [triage] → [wr-mvp] [triage][meta]
Updated•7 years ago
|
Summary: MotionMark CSS bouncing filter circles runs slower than Nightly → [meta] MotionMark CSS bouncing filter circles runs slower than Nightly
Updated•7 years ago
|
Whiteboard: [meta]
Updated•7 years ago
|
Whiteboard: [gfx-noted]
Updated•7 years ago
|
Blocks: stage-wr-nightly
Comment 3•7 years ago
|
||
I just tried running this on my mac with webrender and the score generator seemed totally busted. The actual visual behaviour seemed decent though; highlight-painted-layers shows we don't fallback.
I'm going to consider this fixed.
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
•