Closed Bug 1510630 Opened 6 years ago Closed 6 years ago

3.89 - 9.82% Explicit Memory / Heap Unclassified (windows10-64-qr) regression on push 9ceebf14f260ee222021c47a307fc5210704c330 (Tue Nov 27 2018)

Categories

(Infrastructure & Operations :: RelOps: Windows OS, defect)

x86_64
Windows 10
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: igoldan, Unassigned)

References

Details

(Keywords: perf, regression)

We have detected an awsy regression from push:

https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=0a594d7bf930fd83c3eb5da8daefbd8633c58bb6&tochange=9ceebf14f260ee222021c47a307fc5210704c330

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

Regressions:

 10%  Heap Unclassified windows10-64-qr opt stylo     70,609,521.68 -> 77,543,511.25
  4%  Explicit Memory windows10-64-qr opt stylo       363,130,024.25 -> 377,245,173.58

Improvements:

  5%  Resident Memory windows10-64-qr opt stylo     626,018,623.67 -> 591,918,732.27


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

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
Component: General → RelOps: Windows OS
Product: Testing → Infrastructure & Operations
I think this can be closed as WONTFIX, as it's just an infra update. Unless there's something fishy with the new AWSY baseline on Windows 10.
Flags: needinfo?(rthijssen)
I agree that we should just close it. Leaving ni on :grenade in case he has any thoughts/comments.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
i have nothing to add
Flags: needinfo?(rthijssen)
The graphs did get quite a bit noisier with this change, but that's probably not a reason to revert it. I'll try to look at the noise at some point.
You need to log in before you can comment on or make changes to this bug.