зеркало из https://github.com/mozilla/gecko-dev.git
71de614a1d
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? Differential Revision: https://phabricator.services.mozilla.com/D90894 |
||
|---|---|---|
| .. | ||
| BinaryPath.h | ||
| FileLocation.cpp | ||
| FileLocation.h | ||
| GeckoProcessTypes.h | ||
| IOInterposer.cpp | ||
| IOInterposer.h | ||
| IOInterposerPrivate.h | ||
| LateWriteChecks.cpp | ||
| LateWriteChecks.h | ||
| MainThreadIOLogger.cpp | ||
| MainThreadIOLogger.h | ||
| NSPRInterposer.cpp | ||
| NSPRInterposer.h | ||
| Omnijar.cpp | ||
| Omnijar.h | ||
| PoisonIOInterposer.h | ||
| PoisonIOInterposerBase.cpp | ||
| PoisonIOInterposerMac.cpp | ||
| PoisonIOInterposerStub.cpp | ||
| PoisonIOInterposerWin.cpp | ||
| Services.py | ||
| SmallArrayLRUCache.h | ||
| XPCOM.h | ||
| XPCOMInit.cpp | ||
| XPCOMModule.h | ||
| XPCOMModule.inc | ||
| XREAppData.h | ||
| XREChildData.h | ||
| XREShellData.h | ||
| components.conf | ||
| mach_override.c | ||
| mach_override.h | ||
| moz.build | ||
| nsXPCOM.h | ||
| nsXPCOMCID.h | ||
| nsXPCOMCIDInternal.h | ||
| nsXPCOMPrivate.h | ||
| nsXULAppAPI.h | ||
| perfprobe.cpp | ||
| perfprobe.h | ||
| xpcom_alpha.def | ||
| xrecore.h | ||