cold_load_time regression of 200ms on datazilla

RESOLVED FIXED

Status

Firefox OS
Gaia
P1
normal
RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: bkelly, Unassigned)

Tracking

({perf, regression})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [c= p= u= s=][b2gperf_regression])

(Reporter)

Description

5 years ago
On datazilla we see about a 200ms regression in cold_load_time across the board this morning on master:

  https://datazilla.mozilla.org/b2g/

The gecko revision did not change, so it appears to be something in gaia.  Current gaia range is:

Bad:  https://github.com/mozilla-b2g/gaia/commit/ec885264d885d877d68980c0227058231f18ad09
Good:  https://github.com/mozilla-b2g/gaia/commit/ec885264d885d877d68980c0227058231f18ad09
I have asked to backout this patch for some others performance regression anyway. Can you check datazilla again in a few minutes with new builds without this change.
(Reporter)

Comment 2

5 years ago
Vivien, which commit in particular are you referring to?  Is it ec88526?

I see now I messed up the range above.  The datazilla range actually covers a few commits.  It should be:

Bad:  https://github.com/mozilla-b2g/gaia/commit/ec885264d885d877d68980c0227058231f18ad09
Good:  https://github.com/mozilla-b2g/gaia/commit/d268227c2dcee18dc2568d0b10e347a18ad3e256
(Reporter)

Comment 4

5 years ago
Datazilla confirms this has been resolved.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Reporter)

Updated

4 years ago
Whiteboard: [c= p= u= s=] → [c= p= u= s=][b2gperf_regression]
You need to log in before you can comment on or make changes to this bug.