Closed Bug 1507969 Opened 6 years ago Closed 6 years ago

Collect examples of sites where WebRender performs badly

Categories

(Data Science :: Investigation, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED INACTIVE

People

(Reporter: tdsmith, Assigned: tdsmith)

References

Details

Brief description of the request:

> I need us to get more info/insight into the perf problems we're seeing on the dashboard (the slowness relative to non-WR) -- specifically, the team needs URLs associated with the perf problems so we can try to repro locally and fix the problems.  What's the best way that we can get those?  (Since I understand there are privacy concerns with just grabbing and passing up the URLs.)

Link to any assets:
Discussion document: https://docs.google.com/document/d/1R2ecIqn8W0VTBJrYzmLfnhnXCK-nEvpo69_f_8uayAw/edit?usp=sharing

Is there a specific data scientist you would like or someone who has helped to triage this request:
:tdsmith has been involved with reporting on the current WebRender experiment in nightly/beta.

Maire Reavy is the requester for this work.
Assignee: nobody → tdsmith
Status: NEW → ASSIGNED
Matt Woodrow says they've found crowdsourcy ways to address this for now and don't need data science input.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.