Use a timeout to re-register for cc notifications after |gatherMemory| completes

NEW
Unassigned

Status

()

enhancement
P3
normal
2 years ago
2 years ago

People

(Reporter: erahm, Unassigned)

Tracking

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox57 fix-optional)

Details

Reporter

Description

2 years ago
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

2 years ago
Component: XPCOM → Telemetry
Product: Core → Toolkit
Instead of improving how to use the notification, could we directly record memory measurements into Telemetry from the CC (at some interval)?
Flags: needinfo?(erahm)
Reporter

Comment 2

2 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)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.