Platform/GFX/WebRender Planning: Difference between revisions
Jbonisteel (talk | contribs) (→WebRender Planning: edits) |
Jbonisteel (talk | contribs) (edits to headings) |
||
| Line 16: | Line 16: | ||
Under 'compositor usage' you can see the % of Windows users who are using WebRender: https://firefoxgraphics.github.io/telemetry/#view=windows-features | Under 'compositor usage' you can see the % of Windows users who are using WebRender: https://firefoxgraphics.github.io/telemetry/#view=windows-features | ||
= Q4 Priorities for WR = | |||
The priorities for Q4 (October/November/December) 2019 | The priorities for Q4 (October/November/December) 2019 | ||
| Line 27: | Line 27: | ||
* Make progress on Android | * Make progress on Android | ||
== Perf Infrastructure == | |||
We’d like to be in a position to start shipping WebRender to Windows 10 Intel Laptops in early 2020. We know that battery performance is an issue and we need some infrastructure in place to help resolve that. We need some Our current plan is to re-measure battery performance after landing the following bugs and then determine what else we might need to do to improve this. | We’d like to be in a position to start shipping WebRender to Windows 10 Intel Laptops in early 2020. We know that battery performance is an issue and we need some infrastructure in place to help resolve that. We need some Our current plan is to re-measure battery performance after landing the following bugs and then determine what else we might need to do to improve this. | ||
| Line 45: | Line 45: | ||
</bugzilla> | </bugzilla> | ||
== Correctness == | |||
General correctness bugs are currently tracked the following queries. These are not considered blockers for releases and will be re-triaged to assess importance on a regular basis: | General correctness bugs are currently tracked the following queries. These are not considered blockers for releases and will be re-triaged to assess importance on a regular basis: | ||
| Line 56: | Line 56: | ||
==WR on Android == | |||
Bugs to fix before enabling WR on GeckoView | Bugs to fix before enabling WR on GeckoView | ||
| Line 63: | Line 63: | ||
==Other== | |||
Other bugs we may prioritize in Q4 | Other bugs we may prioritize in Q4 | ||
| Line 80: | Line 80: | ||
==Software Fallback== | |||
* Notes about software backend options: https://github.com/servo/webrender/wiki/Software-backend | * Notes about software backend options: https://github.com/servo/webrender/wiki/Software-backend | ||
Revision as of 19:53, 24 September 2019
WebRender Planning
The purpose of this document is to cover the goals and objectives for WebRender, per quarter.
Roadmaps
Here is a highlevel breakdown of the WebRender roadmap for 2019: https://github.com/orgs/FirefoxGraphics/projects/1
(Note: we are currently working on revamping this to represent a high-level for 2020)
We will track the core pieces of work, per quarter, here: https://github.com/orgs/FirefoxGraphics/projects/4
Where we have shipped
For a list of the various places we have shipped WebRender, see: https://wiki.mozilla.org/Platform/GFX/WebRender_Where
Under 'compositor usage' you can see the % of Windows users who are using WebRender: https://firefoxgraphics.github.io/telemetry/#view=windows-features
Q4 Priorities for WR
The priorities for Q4 (October/November/December) 2019
- Ship our WebRender targets for 70 and 71
- The target for 70 is Windows 10 desktop Intel, with low res screens
- The target for 71 is Windows 10 laptop Nvidia, with low res screens
- Work on performance improvements that will help unblock our ability to ship on more Intel
- Keep on top of important correctness bugs
- Make progress on Android
Perf Infrastructure
We’d like to be in a position to start shipping WebRender to Windows 10 Intel Laptops in early 2020. We know that battery performance is an issue and we need some infrastructure in place to help resolve that. We need some Our current plan is to re-measure battery performance after landing the following bugs and then determine what else we might need to do to improve this.
| ID | Summary | Assigned to |
|---|---|---|
| 1536360 | [meta] Picture caching improvements |
1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Correctness
General correctness bugs are currently tracked the following queries. These are not considered blockers for releases and will be re-triaged to assess importance on a regular basis:
- WR-69: https://mzl.la/2Ngn4en
- WR-70: https://mzl.la/2YR4Abk
- WR-71: https://mzl.la/2MiOEHZ
WR on Android
Bugs to fix before enabling WR on GeckoView
Other
Other bugs we may prioritize in Q4
| ID | Summary | Assigned to |
|---|---|---|
| 1541900 | Add support for outputting RGBA surfaces | Andrew Osmond [:aosmond] (he/him) |
| 1548396 | Support picture caching on child pictures. |
2 Total; 2 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Software Fallback
- Notes about software backend options: https://github.com/servo/webrender/wiki/Software-backend
Other WR Bugzilla Queries and Info
- Untraiged bugs: https://mzl.la/2CsuGmL
- Blocking Next (bugs blocking next release after MVP): bug 1386674
- Blocking Android bugs: bug 1485449
- Blocking Mac bugs: bug 1479789
- Blocking Linux: bug 1491303
To Do: these lists need to be reviewed to reassessed
Triage info:
Mailing list: dev-tech-gfx@lists.mozilla.org
IRC channel: #gfx
Project owner: Maire Reavy