Closed Bug 1666310 Opened 4 years ago Closed 4 years ago

Allow advancing lateWriteChecksStage outside of Nightly

Categories

(Core :: XPCOM, task)

task

Tracking

()

RESOLVED FIXED
83 Branch
Tracking Status
firefox83 --- fixed

People

(Reporter: alexical, Assigned: alexical)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

We want to check late writes to pave the way for fast shutdown outside of Nightly.

We want to collect information on late writes via telemetry. We have been
doing this in Nightly for a while now, but want to do so in beta/release. I
was actually initially unaware of this limitation of the IOInterposer, but
we need the IOInterposer to collect information on late writes, so I would
like to enable it for just early beta, in the hopes that we can catch any
late writes that may be happening, without adding a performance tax onto
release.

Accordingly, is perf the only reason that this was restricted to Nightly?
And if so, did we measure a perf difference, or was this just general
caution regarding the performance impact? Is there anything else to look
out for?

Pushed by dothayer@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3bcf703cd64c
Enable IOInterposer on early beta r=aklotz
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 83 Branch
Summary: Advance lateWriteChecksStage to 3 outside of Nightly → Allow advancing lateWriteChecksStage outside of Nightly
See Also: → 1705042
See Also: → 1705579
See Also: → 1679741
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: