Closed Bug 1677569 Opened 4 years ago Closed 2 years ago

CYCLE_COLLECTOR_MAX_PAUSE regression on May 11, 2020

Categories

(Core :: Cycle Collector, defect)

defect

Tracking

()

RESOLVED INCOMPLETE
Performance Impact low

People

(Reporter: mstange, Unassigned)

References

Details

(Keywords: perf, perf:responsiveness)

We seem to have had a regression in CYCLE_COLLECTOR_MAX_PAUSE during the 78 cycle.

Nightly: https://mzl.la/3lEiOn3
Beta: https://mzl.la/3lEiOn3

:chutten divined the following push log range from the build IDs:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=f44e64a61ed1&tochange=61a83cc0b74b

Olli, does anything stand out from that log?

Flags: needinfo?(bugs)

This is probably a dupe of bug 1658571, which was a regression from bug 1618292, which landed on 5-11. Though it looks like the values didn't quite go down to their previous values when that landed. They did come back down later?

That matches perfectly.

Yes, it does look like the fix didn't bring the numbers back down to the original level, though it did make a noticeable impact - there's a clear decrease on September 24th.

It's possible that the remaining piece is bug 1667316.

This also shows up in the GHOST_WINDOWS telemetry, as you'd expect.

In the 95th percentile, that is. Like this max pause, it hasn't gone down entirely to what it was before.

Whiteboard: [qf] → [qf:p1:responsiveness]
Depends on: 1667316
Whiteboard: [qf:p1:responsiveness] → [qf:p3:responsiveness]
Performance Impact: --- → P3
Whiteboard: [qf:p3:responsiveness]

It looks like a lot of this was fixed, and we're probably not going to make much progress on it this much later.

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(smaug)
Resolution: --- → INCOMPLETE
Component: XPCOM → Cycle Collector
You need to log in before you can comment on or make changes to this bug.