Closed Bug 1575794 Opened 4 months ago Closed 4 months ago

Increase in non-incremental GCs since 13th August

Categories

(Core :: JavaScript: GC, defect, P1)

defect

Tracking

()

RESOLVED FIXED
mozilla70
Tracking Status
firefox-esr60 --- unaffected
firefox-esr68 --- unaffected
firefox68 --- unaffected
firefox69 --- unaffected
firefox70 --- fixed

People

(Reporter: jonco, Assigned: jonco)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

I missed changing this when I changed the threshold to be the incremental trigger rather than the non-incremental one. I'm not entirely sure we need this chech at all - I think it will only happen in the case where we've requested a non-incremental GC but the interrupt hasn't caused one to run yet.

Pushed by jcoppeard@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ee81fd49f90f
Fix INCREMENTAL_TOO_SLOW trigger to check the non-incremental threshold r=sfink
Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70

== Change summary for alert #22957 (as of Wed, 04 Sep 2019 08:07:22 GMT) ==

Improvements:

2% raptor-ares6-firefox windows10-64-shippable-qr opt 59.90 -> 58.45

For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=22957

You need to log in before you can comment on or make changes to this bug.