Page MenuHomePhabricator

[GOAL] Have a way to detect performance regressions to mobile site
Closed, ResolvedPublic

Description

Currently we have no way to determine if a change somewhere has had a negative impact on mobile web's performance until changes hit production. The result of this is that we firefight changes out of our control e.g. introduced by another extension

Let's work this quarter to upcoming prevent this from continuing to be a problem.

We can (and should) leverage the same solution that we will use for desktop: Start testing the code on the way to production. We will collect timing metrics and also number of requests per asset type and size. And then graph them in Grafana as a first step.

Related Objects

StatusSubtypeAssignedTask
ResolvedJdlrobson
ResolvedPeter
Resolvedori
Resolved Spage
ResolvedPeter
DuplicateNone
ResolvedPeter
ResolvedPeter
ResolvedPeter
ResolvedPeter
ResolvedPeter
ResolvedPeter
Resolvedori
ResolvedPeter
ResolvedPeter
ResolvedPeter
ResolvedPeter
ResolvedPeter
Resolvedori
ResolvedPeter
ResolvedPeter
ResolvedPeter
ResolvedPeter

Event Timeline

Jdlrobson raised the priority of this task from to Needs Triage.
Jdlrobson updated the task description. (Show Details)
Jdlrobson moved this task to Goals on the Reading-Web-Planning board.
Jdlrobson added subscribers: Jdlrobson, Peter, JKatzWMF, Tnegrin.
Peter set Security to None.
Jdlrobson claimed this task.

Since we have webpagetest now this seems fixed.