Open Bug 1770758 Opened 2 years ago Updated 2 years ago

3.59% build times (Windows) regression on Tue May 17 2022

Categories

(Developer Infrastructure :: Source Code Analysis, defect, P3)

Tracking

(firefox-esr91 unaffected, firefox100 unaffected, firefox101 unaffected, firefox102 wontfix, firefox103 wontfix)

Tracking Status
firefox-esr91 --- unaffected
firefox100 --- unaffected
firefox101 --- unaffected
firefox102 --- wontfix
firefox103 --- wontfix

People

(Reporter: aesanu, Unassigned)

References

(Regression)

Details

(Keywords: perf-alert, regression)

Perfherder has detected a build_metrics performance regression from push 1254448a9518995f5922080912755262c984bdfd. As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

Ratio Test Platform Options Absolute values (old vs new)
4% build times windows2012-64 plain taskcluster-c4.4xlarge 2,923.97 -> 3,029.00

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests. Please follow our guide to handling regression bugs and let us know your plans within 3 business days, or the offending patch(es) will be backed out in accordance with our regression policy.

For more information on performance sheriffing please see our FAQ.

Flags: needinfo?(krosylight)

I believe maybe it's busy emitting warning to stderr? Bug 1769290 will ultimately reduce the warning count to zero, and we are discussing how to do that.

Could be also that the type name stringification is slowing things down, I wonder what could solve that.

Depends on: 1769290
Flags: needinfo?(krosylight)

Set release status flags based on info from the regressing bug 1766038

(In reply to Kagami :saschanaz from comment #1)

I believe maybe it's busy emitting warning to stderr?

On Windows, the prompt blocks the process until painting whole lines coming from stdout/stderr. Therefore, if the treeherder uses the prompt, this is the cost on Windows specific. Otherwise, if the treeherder does not use the prompt (e.g., just putting only into a file), it means that the build speed for developers is now slower than what this bug reports.

Set release status flags based on info from the regressing bug 1766038

The severity field is not set for this bug.
:andi, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(bpostelnicu)
Severity: -- → S4
Flags: needinfo?(bpostelnicu)
Priority: -- → P3
Product: Firefox Build System → Developer Infrastructure
You need to log in before you can comment on or make changes to this bug.