Render images using quad shaders in simple cases
Categories
(Core :: Graphics: WebRender, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox151 | --- | fixed |
People
(Reporter: nical, Assigned: nical)
References
Details
(Keywords: perf-alert)
Attachments
(6 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review |
The image primitive is WebRender's most complex primitive (surprisingly), due to the many combination of special cases it has to handle, so this bug focuses on porting the simple cases to quad shaders (non-tiled, non-external, and without some of the special logic to handle stacking context snapshots).
| Assignee | ||
Comment 1•6 months ago
|
||
We have bit to spare in the pattern inputs, that seems a bit less error prone to me.
Updated•6 months ago
|
| Assignee | ||
Comment 2•6 months ago
|
||
The textured quad shader is currently only used to composite indirect primitives with a render task per segment.
Once we start segmenting actual image primitives, we need the segments to point to sub-parts of the source image instead of showing the whole image for each segment.
| Assignee | ||
Comment 3•6 months ago
|
||
| Assignee | ||
Comment 4•5 months ago
|
||
| Assignee | ||
Comment 5•5 months ago
|
||
| Assignee | ||
Updated•5 months ago
|
Comment 7•5 months ago
|
||
| bugherder | ||
| Assignee | ||
Comment 8•5 months ago
|
||
This is needed for stacking context snapshots which are fallible. This matches the behavior of the brush image primitive.
Comment 10•5 months ago
|
||
Backed out for causing wrench build bustages
Backout Link
Push with failures
Failure Log
Failure line REFTEST TEST-UNEXPECTED-FAIL | reftests\gradient\linear-hard-stop-repeat-large.yaml == reftests\gradient\linear-hard-stop-repeat-large-ref.yaml | image comparison, max difference: 1, number of differing pixels: 8200 | 8200 num_differences > 0 and <= 255 (allowed 0);
| Assignee | ||
Updated•5 months ago
|
Comment 11•5 months ago
|
||
Comment 12•5 months ago
|
||
Backed out for causing wr failures at iframe-and-main-frame-transition-old-main-new-iframe.html
Backout link
Push with failures
Failure log(s)
| Assignee | ||
Updated•5 months ago
|
Comment 13•5 months ago
|
||
Comment 14•5 months ago
|
||
Comment 15•5 months ago
|
||
Comment 16•5 months ago
|
||
Backed out for causing wpt-meta failures at list-box-important-colors.html.ini
Backout link
Push with failures
Failure log(s)
Comment 17•5 months ago
|
||
| Assignee | ||
Updated•5 months ago
|
| Assignee | ||
Updated•5 months ago
|
Comment 18•5 months ago
|
||
Reverted this because it was causing mochitests failures in browser_bug295977_autoscroll_overflow.js.
- Revert link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | toolkit/content/tests/browser/browser_bug295977_autoscroll_overflow.js | Failed: e should have scrolled vertically
Comment 19•5 months ago
|
||
| Assignee | ||
Updated•5 months ago
|
| Assignee | ||
Updated•5 months ago
|
Comment 20•5 months ago
|
||
Comment 21•5 months ago
|
||
Comment 22•5 months ago
|
||
| bugherder | ||
Comment 23•5 months ago
|
||
Comment 24•5 months ago
|
||
Comment 25•5 months ago
|
||
Backout for causing web failures at content-counter-000-ref.xht
Backout link
Push with failure
Failure log
Failure line TEST-UNEXPECTED-FAIL | /css/CSS2/generated-content/content-counter-016.xht | Testing http://web-platform.test:8000/css/CSS2/generated-content/content-counter-016.xht == http://web-platform.test:8000/css/CSS2/generated-content/content-counter-000-ref.xht
| Assignee | ||
Updated•5 months ago
|
Comment 26•5 months ago
|
||
Comment 27•5 months ago
|
||
| bugherder | ||
| Assignee | ||
Updated•5 months ago
|
Updated•5 months ago
|
Comment 28•5 months ago
|
||
(In reply to Serban Stanca [:SerbanS] from comment #27)
Perfherder has detected a mozperftest performance change from push 09ac39104443a664cd22ee61e510aad4b77453d1.
No action is required from the author; this comment is provided for informational purposes only.
| Improvement | Test | Platform | Options | Absolute values [old vs new] |
|---|---|---|---|---|
| 4% | tab-restore-shopify org.mozilla.fenix:gpu-cpu-time | android-hw-a55-14-0-aarch64-shippable | 693.79 ms -> 663.00 ms | |
| 4% | shopify-applink-startup org.mozilla.fenix:gpu-cpu-time | android-hw-a55-14-0-aarch64-shippable | 732.83 ms -> 703.50 ms |
Need Help or Information?
If you have any questions, please reach out to fbilt@mozilla.com. Alternatively, you can find help on Slack by joining #perf-help, and on Matrix you can find help by joining #perftest.
Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.
Comment 29•4 months ago
|
||
(In reply to Pulsebot from comment #26)
Pushed by nsilva@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/876e94fd7eb9
https://hg.mozilla.org/integration/autoland/rev/09ac39104443
Use the ps_quad_textured shader for image primitives in simple cases. r=gw
Perfherder has detected a browsertime performance change from push 09ac39104443a664cd22ee61e510aad4b77453d1.
No action is required from the author; this comment is provided for informational purposes only.
| Improvement | Test | Platform | Options | Absolute values [old vs new] |
|---|---|---|---|---|
| 3% | google-search-restaurants LastVisualChange (doc) | android-hw-a55-14-0-aarch64-shippable | cold webrender | 792.90 ms -> 772.39 ms |
Need Help or Information?
If you have any questions, please reach out to afinder@mozilla.com. Alternatively, you can find help on Slack by joining #perf-help, and on Matrix you can find help by joining #perftest.
Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.
Updated•4 months ago
|
Description
•