0.3 - 0.39% Base Content JS (linux64-shippable, linux64-shippable-qr, macosx1010-64-shippable, windows10-64-shippable, windows10-64-shippable-qr, windows7-32-shippable) regression on push a8f5dec91d72d4032ced008f847ead37f350193f
Categories
(Core :: JavaScript Engine, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox67 | --- | unaffected |
firefox68 | --- | unaffected |
firefox69 | --- | fixed |
People
(Reporter: igoldan, Assigned: khyperia)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Attachments
(1 file)
We have detected an awsy regression from push:
As author of one of the patches included in that push, we need your help to address this regression.
Regressions:
0.4% Base Content JS windows7-32-shippable opt 3,233,253.33 -> 3,245,760.00
0.3% Base Content JS macosx1010-64-shippable opt 4,084,846.67 -> 4,097,484.00
0.3% Base Content JS linux64-shippable opt 4,083,844.00 -> 4,096,522.67
0.3% Base Content JS windows10-64-shippable-qr opt 4,140,018.67 -> 4,152,893.33
0.3% Base Content JS windows10-64-shippable opt 4,140,072.00 -> 4,153,030.67
0.3% Base Content JS linux64-shippable-qr opt 4,084,141.33 -> 4,096,592.00
You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=21034
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
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 1•5 years ago
|
||
:khyperia if one of the Regressed by bugs is not that related, you can remove it from that list, so we're precise.
Assignee | ||
Comment 2•5 years ago
|
||
Bug 1552229 - Emit field keys in correct order.
is likely irrelevant.
Bug 1547467 - Introduce another scope for .initializers, and remove .localInitializers.
added an unconditional scope around every explicit constructor, to support the implementation of fields - we couldn't make it conditional to only classes with fields, due to the constrained architectural requirements of the parser, without doing some pretty convoluted and difficult-to-maintain hacks.
However, as this did get flagged as a significant memory regression, I have a patch to do a convoluted hack to go back to the memory usage before this patch, by removing that scope in classes without fields.
Assignee | ||
Comment 3•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Pushed by ahauck@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/4ee40acc8b60 Delete .initalizers scope for constructors in classes without fields. r=jorendorff
Comment 6•5 years ago
|
||
bugherder |
Comment 7•5 years ago
|
||
== Change summary for alert #21192 (as of Fri, 31 May 2019 10:55:10 GMT) ==
Improvements:
0% Base Content JS windows7-32-shippable opt 3,148,234.67 -> 3,135,714.67
0% Base Content JS macosx1010-64-shippable opt 3,988,421.33 -> 3,974,598.67
0% Base Content JS linux64-shippable opt 3,987,282.67 -> 3,973,520.00
0% Base Content JS linux64-shippable-qr opt 3,987,336.00 -> 3,973,680.00
0% Base Content JS linux64-shippable opt 3,986,935.33 -> 3,973,888.00
0% Base Content JS windows10-64-shippable-qr opt 4,043,532.00 -> 4,030,672.00
0% Base Content JS windows10-64-shippable opt 4,043,676.00 -> 4,030,577.33
For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=21192
Updated•5 years ago
|
Updated•4 years ago
|
Updated•2 years ago
|
Description
•