Platform/GFX/WebRender Planning: Difference between revisions

From MozillaWiki
< Platform‎ | GFX
Jump to navigation Jump to search
(updating links)
 
(39 intermediate revisions by the same user not shown)
Line 1: Line 1:
= WebRender Planning =  
= WebRender Planning 2019=
 
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<br />
Here is a highlevel breakdown of the WebRender roadmap for 2019: https://github.com/orgs/FirefoxGraphics/projects/1<br />
This document is a more detailed view of that roadmap, including burnup charts.
(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 have we shipped? ==


== Q2 Priorities for WR ==
For a list of the various places we have shipped WebRender, see: https://wiki.mozilla.org/Platform/GFX/WebRender_Where


The priorities for Q2 (April/May/June) 2019
Under 'compositor usage' you can see the % of Windows users who are using WebRender: https://firefoxgraphics.github.io/telemetry/#view=windows-features


=== Correctness ===
= Q4 Priorities for WR =


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:
The priorities for Q4 (October/November/December) 2019


<ul>
* Ship our WebRender targets for  70 and 71
<li>P3 68: https://mzl.la/2Yz2aKt</li>
** The target for 70 is Windows 10 desktop Intel, with low res screens
<li>WR-69: https://mzl.la/2YCP2DQ</li>
** The target for 71 is Windows 10 laptop Nvidia, with low res screens
<li>WR-70: https://mzl.la/2JokPSu</li>
* Work on performance improvements that will help unblock our ability to ship on more Intel
</ul>
* Keep on top of important correctness bugs
* Make progress on Android


=== Foundational work for WR on Android ===
== Perf Infrastructure ==


Complete foundational WebRender on Android work to get things in a ship-able state on HD8 device.
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.


* [https://cpeterso.github.io/burndown/?whiteboard=%5Bwr-amvp Burnup chart]
* [https://cpeterso.github.io/burndown/?whiteboard=%5Bwr-q41 Burnup chart]


<bugzilla>
<bugzilla>
Line 28: Line 37:
   "f3": "status_whiteboard",
   "f3": "status_whiteboard",
   "o3": "anywordssubstr",
   "o3": "anywordssubstr",
   "v3": "[wr-amvp]",
   "v3": "[wr-q41]",


   "resolution": "---",
   "resolution": "---",
Line 36: Line 45:
</bugzilla>
</bugzilla>


=== Continued roll-out of WR ===
== Correctness ==


One of our main objectives throughout 2019 is to bring WebRender to market on core platforms. For Q2, our main deliverables (in addition to the Android work referenced above) are:
General correctness bugs are currently tracked the following queries. These are being re-triaged to assess importance on a regular basis:


* Identify release targets for AMD and Intel desktop, and start work towards it
<ul>
*Identify release target for intel laptops, and start work towards it
<li>WR-71: https://mzl.la/2MiOEHZ</li>
<li>WR-72: https://mzl.la/2pUB7wl</li>
<li>WR-73: https://mzl.la/2JvXrmT</li>
</ul>


The work documented there will help with these specific goals for Q2, as well as our plans throughout the year.
==WR on Android ==


====April====
Bugs to fix before enabling WR on GeckoView


* [https://cpeterso.github.io/burndown/?whiteboard=%5Bwr-april Burnup chart]
https://mzl.la/2FZt46I


<bugzilla>
== General Perf Improvements ==
{
 
  "f3": "status_whiteboard",
Start identifying themes around performance improvements that we can make
  "o3": "anywordssubstr",
 
  "v3": "[wr-april]",
https://pad.mozilla.org/p/wr-perf


  "resolution": "---",
==Other==
  "include_fields": "id,summary,assigned_to",
  "order": "resolution,assigned_to,id"
}
</bugzilla>


====May====
Other bugs we may prioritize in Q4
* [https://cpeterso.github.io/burndown/?whiteboard=%5Bwr-may Burnup chart]


<bugzilla>
<bugzilla>
Line 68: Line 75:
   "f3": "status_whiteboard",
   "f3": "status_whiteboard",
   "o3": "anywordssubstr",
   "o3": "anywordssubstr",
   "v3": "[wr-may]",
   "v3": "[wr-q4]",


   "resolution": "---",
   "resolution": "---",
Line 76: Line 83:
</bugzilla>
</bugzilla>


====June====


* [https://cpeterso.github.io/burndown/?whiteboard=%5Bwr-june Burnup chart]
==Software Fallback==
 
<bugzilla>
{
  "f3": "status_whiteboard",
  "o3": "anywordssubstr",
  "v3": "[wr-june]",


  "resolution": "---",
* Notes about software backend options: https://github.com/servo/webrender/wiki/Software-backend
  "include_fields": "id,summary,assigned_to",
  "order": "resolution,assigned_to,id"
}
</bugzilla>


== Other WR Bugzilla Queries and Info==
== Other WR Bugzilla Queries and Info==

Latest revision as of 14:16, 19 November 2019

WebRender Planning 2019

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 have we 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.

Full Query
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 being re-triaged to assess importance on a regular basis:

WR on Android

Bugs to fix before enabling WR on GeckoView

https://mzl.la/2FZt46I

General Perf Improvements

Start identifying themes around performance improvements that we can make

https://pad.mozilla.org/p/wr-perf

Other

Other bugs we may prioritize in Q4

Full Query
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

Other WR Bugzilla Queries and Info

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

Retrieved from "https://wiki.mozilla.org/index.php?title=Platform/GFX/WebRender_Planning&oldid=1220441"