Closed
Bug 1281791
Opened 8 years ago
Closed 7 years ago
Default to not recording Telemetry histograms in the child processes
Categories
(Toolkit :: Telemetry, defect, P3)
Toolkit
Telemetry
Tracking
()
RESOLVED
DUPLICATE
of bug 1335343
Tracking | Status | |
---|---|---|
firefox50 | --- | affected |
People
(Reporter: gfritzsche, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [measurement:client])
Currently we are only using a known small set of histograms for the content processes.
We should use the format changes now and default to not recording histograms in any child processes.
We'll need to add a field for Histograms.json that allows specifying which Histograms should be recorded in which process type.
Comment 1•8 years ago
|
||
How many histograms would this change affect?
Reporter | ||
Comment 2•8 years ago
|
||
This would affect most histograms.
We still need to clear up whether that is actually ok with the users, sorry for leaving that part out.
From what i heard anecdotally from e10s analysis etc., it seems that very few content process histograms are actually being looked at.
If that still is the case, we should - as soon as possible - start to default the other histograms to not record there, because reaching out for all individual histograms will be hard.
Comment 3•7 years ago
|
||
Looks like we took care of this over in bug 1335343
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•