715380 - Provide telemetry on timers created by webpages

Status: RESOLVED FIXED

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

Description

[(dormant account)]

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.

Comment 1

[Nathan Froyd [:froydnj]]

(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?

Comment 2

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

There are XPCOM timers (nsTimerImpls) and DOM timers (nsTimeouts), and they are distinct but related entities.

Comment 3

[(dormant account)]

I think bug 715953 is sufficient to show that we need to be more clever with our timers.

Comment 4

[(dormant account)]

I keep accidentally using a non-existent snappy:p4 priority

Comment 5

[Nathan Froyd [:froydnj]]

Dependent bugs fixed.  Closing.