Closed
Bug 1229710
Opened 9 years ago
Closed 6 years ago
Experiments should not be initialized before the 60s delay
Categories
(Toolkit :: Telemetry, defect)
Toolkit
Telemetry
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: Dexter, Unassigned)
Details
(Whiteboard: [measurement:client])
In bug 1217282 we found that experiments are being initialized before the 60s delayed Telemetry init, possibly having a negative effect on startup performance.
We should investigate and fix this issue by making experiments init after the 60s delay.
Reporter | ||
Updated•9 years ago
|
Points: --- → 2
Priority: -- → P3
Whiteboard: [measurement:client]
Comment 1•9 years ago
|
||
There is one exception here - if we have an active experiment (signaled with the pref experiments.activeExperiment), experiments should init early in startup.
Updated•9 years ago
|
Priority: P3 → P4
Comment 2•6 years ago
|
||
Passing to Shield for prioritization on their planning schedule.
status-firefox45:
affected → ---
Component: Telemetry → General
Priority: P4 → --
Product: Toolkit → Shield
Version: Trunk → unspecified
Comment 3•6 years ago
|
||
I think the experiments mentioned in bug 1217282 are entirely unrelated to Shield and Normandy, and are in fact the now-removed Telemetry Experiments platform. I think that this was correctly categorized before. Additionally I think this bug can be closed as the feature isn't present at all anymore.
Component: General → Telemetry
Flags: needinfo?(gfritzsche)
Product: Shield → Toolkit
Comment 4•6 years ago
|
||
Yes, this was about Telemetry experiments, which is gone.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(gfritzsche)
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•