Child processes on Android have pointless telemetry timers and IPCs
Categories
(Toolkit :: Telemetry, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox128 | --- | fixed |
People
(Reporter: florian, Assigned: chutten|PTO)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
While profiling Fenix, I noticed
TelemetryIPCAccumulator::IPCTimerFired 2s timers and PContent::Msg_AccumulateChildHistograms, PContent::Msg_AccumulateChildKeyedHistograms and PContent::Msg_RecordDiscardedData IPCs sent to the parent process.
Chutten confirmed in #glean that these are not wanted anymore on Android.
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Comment 1•1 year ago
|
||
Profile showing these IPCs happening 13 times in 30s, including 9 times when Fenix was not even on screen: https://share.firefox.dev/3WFxoA4
| Assignee | ||
Comment 2•1 year ago
|
||
Telemetry IPC batches and transports instrumentation actions on histograms, keyed histograms, scalars, keyed scalars, and events.
Since bug 1877576, none of those actions result in any data collection on Android.
We can definitely no-op the Accumulator and 0-size its storage... but we may be able to do even more by, say, no-op-ing for Android the surface Legacy Telemetry APIs that call into the IPC accumulator.
This bug will be about:
- Doing a quick scan to see how far "up" we can stop processing android Legacy Telemetry actions
- Excluding from compile any implementation we can
- Turning off Legacy Telemetry tests in Android that depend on those APIs
| Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
| Assignee | ||
Comment 4•1 year ago
|
||
Stuck to the minimal implementation this time around due to time pressures, but if and when needed we could stub all implementations of all exported telemetry headers on builds heading for mobile platforms.
Comment 6•1 year ago
|
||
| bugherder | ||
Description
•