Open Bug 1191318 Opened 10 years ago Updated 3 years ago

Investigate ping generation on "idle" notifications

Categories

(Toolkit :: Telemetry, defect, P4)

Product:
Toolkit
Component:
Telemetry
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox41 --- affected
firefox42 --- affected

People

(Reporter: Dexter, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [unifiedTelemetry] [measurement:client])

We may trigger ping generations etc. when we receive the "idle" notification instead of only rescheduling timers - do we have to?
Blocks: 1122482
status-firefox41: --- → affected
Whiteboard: [unifiedTelemetry]
Blocks: 1201022
No longer blocks: 1122482
ni?dexter for context - what concern did we have with generating pings on idle?
Flags: needinfo?(alessio.placitelli)
Priority: -- → P3
Whiteboard: [unifiedTelemetry] → [unifiedTelemetry] [measurement:client]
This bug was about investigating the opportunity to generate pings which required gathering data immediately after the user became "idle", without waiting for the appropriate scheduler cycle This way gathering can be completed before the user becomes active again.
Flags: needinfo?(alessio.placitelli)
Going from comment 0, i vaguely remember that on "idle" we: * in the schedulers "idle" handler we do reschedule timers * the "idle" handler may also trigger ping generation * that may be undesired
Priority: P3 → P4
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.