Closed Bug 715380 Opened 10 years ago Closed 9 years ago

Provide telemetry on timers created by webpages

Categories

(Core :: DOM: Core & HTML, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: taras.mozilla, Assigned: froydnj)

References

(Blocks 1 open bug)

Details

(Whiteboard: [snappy:p3])

We need something to give us an idea of how much of a problem timers are (and measure progress).
* telemetry on how many setTimeouts within one nsITimer run
* telemetry on how many timeouts are attached to a window
* telemetry on how many background timeouts are scheduled within 30seconds

Nathan, can you dive into this? bz will guide you as to where to stick the probes.
(In reply to Taras Glek (:taras) from comment #0)
> We need something to give us an idea of how much of a problem timers are
> (and measure progress).
> * telemetry on how many setTimeouts within one nsITimer run
> * telemetry on how many timeouts are attached to a window
> * telemetry on how many background timeouts are scheduled within 30seconds

Is there a reason this bug is in DOM, but nsTimerImpl is in xpcom?  I guess for the first bit one wants to modify nsTimerImpl, but for the other two, some DOM plumbing will be required?
There are XPCOM timers (nsTimerImpls) and DOM timers (nsTimeouts), and they are distinct but related entities.
Depends on: 715947
Depends on: 715950
Depends on: 715953
I think bug 715953 is sufficient to show that we need to be more clever with our timers.
Whiteboard: [snappy] → [snappy:p4]
I keep accidentally using a non-existent snappy:p4 priority
Whiteboard: [snappy:p4] → [snappy:p3]
Dependent bugs fixed.  Closing.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.