MozillaWiki

Platform/GFX/WebRender Planning: Difference between revisions

Page Discussion

Platform/GFX/WebRender Planning (view source)

Revision as of 14:16, 19 November 2019

113 bytes added ,  19 November 2019
→‎WebRender Planning: notes
(edits)
 
(27 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? ==


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


== Q3 Priorities for WR ==
Under 'compositor usage' you can see the % of Windows users who are using WebRender: https://firefoxgraphics.github.io/telemetry/#view=windows-features


The priorities for Q3 (July/August/September) 2019
= Q4 Priorities for WR =


=== Correctness ===
The priorities for Q4 (October/November/December) 2019


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:
* 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


<ul>
== Perf Infrastructure ==
<li>P3 68: https://mzl.la/2Yz2aKt</li>
<li>WR-69: https://bugzilla.mozilla.org/show_bug.cgi?id=wr-69</li>
<li>WR-70: https://bugzilla.mozilla.org/show_bug.cgi?id=wr-70</li>
</ul>


=== Continued roll-out of WR ===
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.


One of our main objectives throughout 2019 is to bring WebRender to market on core platforms. For Q3, our main deliverables (in addition to the Android work referenced above) are:
* [https://cpeterso.github.io/burndown/?whiteboard=%5Bwr-q41 Burnup chart]


* Identify target for initial WebRender  release on Android
<bugzilla>
* Identify further Android releases/devices to target
{
  "f3": "status_whiteboard",
  "o3": "anywordssubstr",
  "v3": "[wr-q41]",


WebRender on Desktop
  "resolution": "---",
  "include_fields": "id,summary,assigned_to",
  "order": "resolution,assigned_to,id"
}
</bugzilla>


* Ship WebRender to more platforms each release for the remainder of 2019
== Correctness ==
* Intel Windows 10 with low-res (less than 4K) screens - ride the trains for 69
** Update (08/19) we are moving this target to 70 due to this issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1556634


Other
General correctness bugs are currently tracked the following queries. These are being re-triaged to assess importance on a regular basis:


* V1 plan for non-WebRender code path options
<ul>
* Determine how to measure battery impact of WebRender
<li>WR-71: https://mzl.la/2MiOEHZ</li>
 
<li>WR-72: https://mzl.la/2pUB7wl</li>
The work documented there will help with these specific goals for Q3, as well as our plans throughout the year.
<li>WR-73: https://mzl.la/2JvXrmT</li>
</ul>


====WR on Android ====
==WR on Android ==


Bugs to fix before enabling WR on GeckoView
Bugs to fix before enabling WR on GeckoView
Line 46: Line 61:
https://mzl.la/2FZt46I
https://mzl.la/2FZt46I


== General Perf Improvements ==


====July====
Start identifying themes around performance improvements that we can make
 
* [https://cpeterso.github.io/burndown/?whiteboard=%5Bwr-july Burnup chart]


<bugzilla>
https://pad.mozilla.org/p/wr-perf
{
  "f3": "status_whiteboard",
  "o3": "anywordssubstr",
  "v3": "[wr-july]",


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


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


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


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


====September====


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


<bugzilla>
* Notes about software backend options: https://github.com/servo/webrender/wiki/Software-backend
{
  "f3": "status_whiteboard",
  "o3": "anywordssubstr",
  "v3": "[wr-sept]",
 
  "resolution": "---",
  "include_fields": "id,summary,assigned_to",
  "order": "resolution,assigned_to,id"
}
</bugzilla>


== Other WR Bugzilla Queries and Info==
== Other WR Bugzilla Queries and Info==
Jbonisteel
428

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1216237...1220441"