Closed Bug 1447573 Opened 6 years ago Closed 6 years ago

8.72% Strings PerfStripCharsWhitespace (osx-10-10) regression on push ea926eb29682 (Mon Mar 12 2018)

Categories

(Core :: Disability Access APIs, defect)

Unspecified
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: igoldan, Unassigned)

References

Details

(Keywords: perf, regression)

We have detected a platform microbenchmarks regression from push:

https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?changeset=ea926eb2968226a0c58a2f7e2fc173035cd49ca8

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

Regressions:

  9%  Strings PerfStripCharsWhitespace osx-10-10 opt      314,041.33 -> 341,420.08


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

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://developer.mozilla.org/en-US/docs/Mozilla/Performance/Automated_Performance_Testing_and_Sheriffing/Platform_Microbenchmarks
Component: Untriaged → Disability Access APIs
Product: Firefox → Core
:surkov Bug 1257669 seems to have caused this perf regression on March 12. I filed this tracking bug to check whether this makes sense or not. What are your thoughts?

Fortunately, a recent change canceled this regression.
Flags: needinfo?(surkov.alexander)
FYI Strings * tests are highly sensitive and very often raise false alerts.
that patch was all about assertions in debug builds. It should have zero effect for release builds. Is it a false positive indeed?
Flags: needinfo?(surkov.alexander)
(In reply to alexander :surkov from comment #3)
> that patch was all about assertions in debug builds. It should have zero
> effect for release builds. Is it a false positive indeed?

Thanks for sharing this.

Well, for the last month, the test ran as bi-modal.

Then either bug 1257669 or other bug which landed around that time made the test return the upper values.
Switching from multi-modal to uni-modal sometimes is even desired.

:jmaher I'm into resolving this as WORKSFORME. Do you have other thoughts?
Flags: needinfo?(jmaher)
sometimes a switch in modality is a regression or improvement, often it is just random luck.  I am fine with worksforme.
Flags: needinfo?(jmaher)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.