Closed Bug 1532224 Opened 5 years ago Closed 5 years ago

0.3% Base Content JS (windows7-32) regression on push 5b59b3bf72d880c4b3e05156ef329854075b24f8 (Thu Feb 28 2019)

Categories

(WebExtensions :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: Bebe, Unassigned)

References

Details

(Keywords: perf, regression)

We have detected an awsy regression from push:

https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?changeset=5b59b3bf72d880c4b3e05156ef329854075b24f8

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

Regressions:

0% Base Content JS windows7-32 pgo stylo 3,189,029.33 -> 3,198,567.33

Improvements:

5% Resident Memory linux64 pgo stylo 633,812,787.15 -> 602,692,747.97
2% Explicit Memory linux64 pgo stylo 352,122,316.30 -> 344,945,056.81

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

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 jobs in a pushlog format.

To learn more about the regressing test(s), please see: https://wiki.mozilla.org/AWSY/Tests

Blocks: 1518863, 1521698
Product: Testing → WebExtensions
Version: Version 3 → unspecified

We're just going to have to eat this for the moment. We can't fix bug 1518863 without adding more JS to the content process, and I have extension framework memory improvements planned for the near future.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.