Closed Bug 822844 Opened 12 years ago Closed 8 years ago

Please explain why TELEMETRY_DELAY is 60s

Categories

(Toolkit :: Telemetry, defect)

Product:
Toolkit
Component:
Telemetry
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: espindola, Unassigned)

Details

While working on bug 822812 I noticed telemetry already had a startup delay (TELEMETRY_DELAY) and that it was much larger than what we were using (60s instead of 5 something). In that bug we just removed the second timer and added code to the existing one, but we could not figure out if our choice of 5 seconds was too short or the existing delay is too long (or if in the end we do need two timers).
Assignee: taras.mozilla → nobody
Status: ASSIGNED → NEW
As far as i know, this is a rather arbitrary choice for performance reasons. Telemetry doesn't need to launch all its work early in the session.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.