Closed Bug 1520451 Opened 5 years ago Closed 5 years ago

43.58% raptor-tp6-microsoft-firefox (osx-10-10) regression on push aa43ce6e3442f05ec14243a2f1311012bc6b51cb (Tue Jan 15 2019)

Categories

(Core :: Gecko Profiler, defect)

Unspecified
macOS
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: igoldan, Unassigned)

References

Details

(Keywords: perf, regression)

Raptor has detected a Firefox performance regression from push:

https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=5101144bde6a5c05419f4f3b2925a15ca696b1a1&tochange=aa43ce6e3442f05ec14243a2f1311012bc6b51cb

As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

44% raptor-tp6-microsoft-firefox osx-10-10 opt 1,844.07 -> 2,647.70

You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=18750

On the page above you can see an alert for each affected platform as well as a link to a graph showing the history of scores for this test. There is also a link to a Treeherder page showing the Raptor jobs in a pushlog format.

To learn more about the regressing test(s) or reproducing them, please see: https://wiki.mozilla.org/Performance_sheriffing/Raptor

*** Please let us know your plans within 3 business days, or the offending patch(es) will be backed out! ***

Our wiki page outlines the common responses and expectations: https://wiki.mozilla.org/Performance_sheriffing/Talos/RegressionBugsHandling

Component: General → Gecko Profiler
Product: Testing → Core
Flags: needinfo?(rjesup)

The patch contained 5 separate bugs. :rjesup out of the bugs listed bellow, which one is more related to this perf regression?

bug 1518030
bug 1517272
bug 1514514
bug 1514513
bug 1508837

(In reply to Dave Hunt [:davehunt] [he/him] ⌚️UTC from comment #2)

I would suspect bug 1514513 as looking at the subtests, the regression only affected ttfi: https://treeherder.mozilla.org/perf.html#/graphs?series=autoland,1825059,1,10&series=autoland,1825060,1,10&series=autoland,1825061,1,10

Good point!

Blocks: 1514513
Keywords: stalled

TTFI is highly variable due to how it works, and we don't alert on it - but especially in a test without loadtime, TTFI has a major impact on a geomean'd result from all the subtests - as happened here.

We likely should simply ignore this.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(rjesup)
Resolution: --- → WONTFIX

(In reply to Randell Jesup [:jesup] from comment #4)

TTFI is highly variable due to how it works, and we don't alert on it - but especially in a test without loadtime, TTFI has a major impact on a geomean'd result from all the subtests - as happened here.

We likely should simply ignore this.

Are you proposing us to avoid outputting TTFI values in absence of loadtime values? This sounds like a harness update for raptor-tp6.

Flags: needinfo?(rjesup)

We've turned off TTFI on raptor for now. I still want to know why TTFI reacted this way

Flags: needinfo?(rjesup)
You need to log in before you can comment on or make changes to this bug.