8% Regression on AWFY-Jetstream2-base64-SP-Average around Feb1
Categories
(Core :: Performance, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox110 | --- | unaffected |
firefox111 | --- | wontfix |
firefox112 | --- | wontfix |
People
(Reporter: mayankleoboy1, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Go to https://arewefastyet.com/win10/benchmarks/raptor-desktop-jetstream2?numDays=60
Look at base64-SP-Average
Suspected: bug 1808673
Reporter | ||
Updated•2 years ago
|
Comment 1•2 years ago
|
||
This bug has been marked as a regression. Setting status flag for Nightly to affected
.
Comment 2•2 years ago
|
||
Likely a regression from bug 1808673.
Comment 3•2 years ago
|
||
Trying to figure out how to run base64-SP.
But I don't think we should backout bug 1808673, since it improved ReactJS-Todo quite a bit
https://treeherder.mozilla.org/perfherder/graphs?highlightAlerts=1&highlightChangelogData=1&highlightCommonAlerts=0&series=autoland,3912919,1,13&timerange=5184000
Comment 4•2 years ago
|
||
Set release status flags based on info from the regressing bug 1808673
Comment 5•2 years ago
|
||
:smaug did you make an progress in your investigation in comment 3?
What is the impact the for 111 release or the severity?
Comment 6•2 years ago
|
||
I pinged :smaug on matrix and was told this shouldn't block for 111, marking fix-optional
Reporter | ||
Comment 7•2 years ago
|
||
FWIF, the numbers have gone back up to roughly the previous range.
But not sure which bug actually improved the score.
Comment 8•2 years ago
|
||
Probably Bug 1817767, not sure how though :)
But I think this is now WFM
Comment 9•2 years ago
|
||
And thanks Mayank for checking that!
Updated•2 years ago
|
Description
•