Closed Bug 1589638 Opened 5 years ago Closed 5 years ago

6.78 - 44.59% Explicit Memory / Heap Unclassified / Images / JS / Resident Memory (linux64,macosx1014-64-shippable, windows10-64) regression on push 843409fd89e639b0e08cba8737b3945dd27b2b08 (Thu October 17 2019)

Categories

(Testing :: Performance, defect)

Version 3
defect
Not set
normal

Tracking

(firefox-esr68 unaffected, firefox70 unaffected, firefox71 fixed)

RESOLVED FIXED
mozilla71
Tracking Status
firefox-esr68 --- unaffected
firefox70 --- unaffected
firefox71 --- fixed

People

(Reporter: Bebe, Assigned: marauder)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

We have detected an awsy regression from push:

https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=843409fd89e639b0e08cba8737b3945dd27b2b08

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

Regressions:

45% Images linux64-shippable-qr opt 5,663,587.24 -> 8,189,190.08
43% Images linux64-qr opt 5,732,029.34 -> 8,191,782.71
27% Images windows10-64-qr opt 7,976,469.14 -> 10,169,443.76
27% Images macosx1014-64-shippable opt 4,331,257.71 -> 5,519,191.44
27% Images windows10-64-shippable-qr opt 7,991,217.82 -> 10,164,887.88
27% Images windows7-32 opt 4,787,886.77 -> 6,058,120.50
23% Heap Unclassified macosx1014-64-shippable opt stylo tp6 158,958,939.09 -> 196,270,542.63
22% Images windows7-32-shippable opt 4,839,442.84 -> 5,920,970.04
22% Images linux64 opt 4,490,655.67 -> 5,459,022.58
21% Images linux64-stylo-sequential opt 4,463,107.00 -> 5,406,178.67
20% Images linux64-shippable opt 4,400,086.71 -> 5,266,114.66
19% Resident Memory macosx1014-64-shippable opt stylo tp6 561,319,041.59 -> 669,694,664.00
17% Heap Unclassified linux64 opt stylo tp6 114,890,938.94 -> 134,911,110.99
16% Resident Memory linux64 opt stylo tp6 747,461,877.75 -> 865,231,079.15
15% Explicit Memory macosx1014-64-shippable opt stylo tp6 539,364,880.26 -> 621,140,053.91
15% Resident Memory linux64-shippable opt stylo tp6 750,079,515.26 -> 863,693,077.20
15% Images windows10-64-shippable opt 5,362,784.98 -> 6,173,682.86
15% Explicit Memory linux64 opt stylo tp6 512,396,392.51 -> 586,842,886.52
14% JS linux64 opt stylo tp6 202,892,002.36 -> 232,207,068.65
14% JS windows7-32 opt stylo tp6 155,106,886.69 -> 177,338,048.80
14% JS linux64-shippable-qr opt stylo tp6 202,622,485.25 -> 230,883,353.91
14% JS windows7-32-shippable opt stylo tp6 156,161,119.40 -> 177,951,221.58
14% Explicit Memory linux64-shippable opt stylo tp6 509,875,211.00 -> 580,935,807.86
14% JS windows10-64-qr opt stylo tp6 207,433,475.02 -> 236,329,242.44
13% JS linux64-shippable opt stylo tp6 202,800,992.16 -> 230,136,677.10
13% JS windows10-64-shippable-qr opt stylo tp6 208,268,019.62 -> 235,831,775.56
13% JS macosx1014-64-shippable opt stylo tp6 203,122,020.81 -> 229,881,854.30
13% JS windows10-64 opt stylo tp6 207,263,391.00 -> 234,463,975.81
13% Resident Memory windows10-64 opt stylo tp6 732,134,344.94 -> 827,894,639.46
13% JS linux64-qr opt stylo tp6 205,112,054.92 -> 231,775,836.68
12% Explicit Memory windows10-64 opt stylo tp6 472,474,894.33 -> 531,112,065.19
12% Explicit Memory windows10-64-qr opt stylo tp6 488,034,795.72 -> 547,870,345.72
12% Resident Memory windows7-32-shippable opt stylo tp6 691,302,320.33 -> 774,950,843.09
12% Resident Memory windows7-32-shippable opt stylo tp6 690,416,450.64 -> 773,777,467.59
12% Explicit Memory windows10-64-shippable-qr opt stylo tp6 490,730,394.05 -> 548,460,650.90
12% Resident Memory linux64-shippable-qr opt stylo tp6 927,161,949.92 -> 1,034,058,226.26
11% Resident Memory linux64-qr opt stylo tp6 919,038,834.45 -> 1,024,568,993.27
11% Explicit Memory linux64-shippable-qr opt stylo tp6 638,000,990.77 -> 707,775,100.02
11% Resident Memory windows10-64-qr opt stylo tp6 708,273,874.25 -> 785,034,318.56
11% Explicit Memory windows7-32-shippable opt stylo tp6 391,598,996.19 -> 433,942,300.95
11% Explicit Memory windows7-32 opt stylo tp6 391,577,113.33 -> 433,711,645.06
11% Explicit Memory linux64-qr opt stylo tp6 636,390,200.60 -> 704,703,656.90
10% Explicit Memory windows10-64-shippable opt stylo tp6 471,750,953.53 -> 520,509,030.85
10% Resident Memory windows10-64-shippable-qr opt stylo tp6 722,088,302.11 -> 794,499,209.03
10% Heap Unclassified linux64-qr opt stylo tp6 228,710,206.64 -> 250,910,924.92
10% JS windows10-64-shippable opt stylo tp6 204,709,263.67 -> 224,515,309.62
8% Resident Memory windows10-64-shippable opt stylo tp6 675,468,561.98 -> 729,730,649.77
7% Images windows10-64 opt 5,769,713.81 -> 6,160,890.79

Improvements:

14% Images windows10-64-shippable opt stylo tp6 8,055,166.51 -> 6,963,351.96
12% Images macosx1014-64-shippable opt stylo tp6 7,634,611.88 -> 6,736,937.81
11% Images linux64 opt stylo tp6 7,307,233.59 -> 6,487,854.86
9% Images linux64-shippable opt stylo tp6 7,245,700.79 -> 6,558,163.80
9% Images windows10-64 opt stylo tp6 8,356,679.43 -> 7,620,684.02
6% Images linux64-qr opt stylo tp6 8,245,709.36 -> 7,757,090.90
3% Resident Memory windows10-64-qr opt 569,434,443.35 -> 549,936,884.77
3% Resident Memory windows10-64-shippable-qr opt 573,999,682.22 -> 555,855,102.38
2% JS windows10-64-qr opt 113,500,175.13 -> 111,081,467.46

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

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: 1578356
Regressed by: 1567122
Blocks: 1592626
No longer blocks: 1592626

The priority flag is not set for this bug.
:davehunt, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dave.hunt)
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Flags: needinfo?(dave.hunt)
Assignee: nobody → marian.raiciof
Target Milestone: --- → mozilla71
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.