1.98 - 2.06% Base Content Heap Unclassified (linux64-shippable, linux64-shippable-qr) regression on push 61ae24d322cb05bec32cf7620778f15a2e6908e5 (Thu May 23 2019)
Categories
(Core :: General, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox-esr68 | --- | unaffected |
firefox67 | --- | unaffected |
firefox67.0.1 | --- | unaffected |
firefox68 | --- | unaffected |
firefox69 | --- | wontfix |
firefox70 | --- | wontfix |
firefox71 | --- | fix-optional |
People
(Reporter: igoldan, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
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:
2% Base Content Heap Unclassified linux64-shippable opt 5,496,701.33 -> 5,609,914.00
2% Base Content Heap Unclassified linux64-shippable-qr opt 5,493,604.33 -> 5,602,432.33
You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=21071
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•6 years ago
|
Reporter | ||
Updated•6 years ago
|
![]() |
||
Comment 1•6 years ago
|
||
I don't think there is enough reason for us here to block the dependency updates (namely, rand and parking_lot), given that only Linux is negatively affected. I'll work with library authors to figure out if that can be fixed upstream, starting with https://github.com/Amanieu/parking_lot/issues/143
Reporter | ||
Updated•6 years ago
|
Comment 2•6 years ago
|
||
P1 due to it being a regression on Fx69.
:kvark, since the bug is assigned to you, feel free to adjust the priority.
Updated•6 years ago
|
![]() |
||
Comment 3•6 years ago
|
||
![]() |
||
Comment 5•6 years ago
|
||
original: 5584776 unclassified mem (unfixed), which leaves me puzzled a bit as to why the previous try (rolling back mozurl) shows more...
Comment 6•6 years ago
|
||
(In reply to Dzmitry Malyshau [:kvark] from comment #5)
original: 5584776 unclassified mem (unfixed), which leaves me puzzled a bit as to why the previous try (rolling back mozurl) shows more...
Are you comparing with the same base revision? As in starting w/ base revision A you do a try run w/ a few retriggers, then you apply the mozurl change (B) to test A + B, then you try just the u2fhid change (C) to test A + C, etc. Our fission memory wiki give a quick description of this workflow.
![]() |
||
Comment 7•6 years ago
|
||
Yes, Eric, I'm working off the same revision in these tests
Comment 8•6 years ago
|
||
(In reply to Dzmitry Malyshau [:kvark] from comment #7)
Yes, Eric, I'm working off the same revision in these tests
Okay, but that's on top of your local equivalent of https://hg.mozilla.org/mozilla-central/rev/61ae24d322cb which is what this bug says regressed things (which might be what you intended). It might be worth starting totally clean.
![]() |
||
Comment 9•6 years ago
|
||
Oh, good point! I'll start off a cleaner base.
![]() |
||
Comment 10•6 years ago
|
||
Clean state patches based off rev 3f656afb0c08aae2ed9b2ebe4128bac71146c679 :
(the parking lot rolls include mozurl changes)
Also filed https://github.com/rust-random/rand/issues/820 for Rand maintainers.
![]() |
||
Comment 11•6 years ago
|
||
Wow, all of these tries show about the same result of 159xxxx on "Base Content Heap Unclassified opt", which means they aren't addressing the regression, hmm
![]() |
||
Comment 13•6 years ago
|
||
Patricia, we should move it to 70, it's not critical.
Updated•6 years ago
|
![]() |
||
Updated•6 years ago
|
![]() |
||
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•5 years ago
|
Updated•4 years ago
|
Comment 14•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last months and this bug has priority 'P1'.
:overholt, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Description
•