Open
Bug 1377585
Opened 7 years ago
Updated 2 years ago
Use a timeout to re-register for cc notifications after |gatherMemory| completes
Categories
(Toolkit :: Telemetry, enhancement, P3)
Toolkit
Telemetry
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox57 | --- | fix-optional |
People
(Reporter: erahm, Unassigned)
References
Details
From bug 1375281, comment 14 we would like to stop always observing the cc-end notification. Instead we want to:
#1 - Register for notification
#2 - Get notified, unregister
#3 - Dispatch the idle |gatherMemory| request
#4 - Issue a setTimeout to re-register at the end of |gatherMemory|
This will hopefully avoid redundant round trips where we observe the notification, calculate the amount of time that's passed and then ignore the notification.
Reporter | ||
Updated•7 years ago
|
Component: XPCOM → Telemetry
Product: Core → Toolkit
Comment 1•7 years ago
|
||
Instead of improving how to use the notification, could we directly record memory measurements into Telemetry from the CC (at some interval)?
Updated•7 years ago
|
Flags: needinfo?(erahm)
Reporter | ||
Comment 2•7 years ago
|
||
(In reply to Georg Fritzsche [:gfritzsche] from comment #1)
> Instead of improving how to use the notification, could we directly record
> memory measurements into Telemetry from the CC (at some interval)?
We're explicitly trying to avoid adding overhead to CC for telemetry measurements.
Flags: needinfo?(erahm)
Updated•7 years ago
|
Priority: -- → P3
Updated•7 years ago
|
status-firefox57:
--- → fix-optional
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•