671044 - batch 'o telemetry metrics for general things

Status: RESOLVED WONTFIX

(Firefox :: General, defect)

Description

[Justin Dolske [:Dolske]]

Misc
    Number of popups (by flavor, alerts, annoying popups, form postdata) (+1)
    How many people have enabled do not track?
    how many resources are loaded vs. cache hits (already in there?)
    how often is document.write() encountered, and what did it write to the DOM
    network utilization, like parallel connections in resource downloads (+1)
    time spent for a tab that is inactive/in the background (web perf -- PageVisibility)
    page reflows/repaints (may already be there?)
    when our "clamping" has to kick in for setTimeout()/setInterval() loops
    Time for Firefox menu/context menu to popup
    UI events: https://spreadsheets.google.com/spreadsheet/ccc?key=0AjIcGNW1bFV5dEFHMENLNzFsRXIyaVFoTFNpUHBTb3c&authkey=CMTsjOIJ&hl=en_US#gid=0
    Awesomebar suggestion times (should not slowdown searches though) (+1)
    Number of add-ons installed, enabled, disabled, from 3rd party, number of jetpacks
    jetpacks? or restartless addons? (they're different, damnit!)
    time between opening a menu and selecting a menu
    delayedStartup time / BrowserShutdown time

Comment 1

[Dietrich Ayala (:dietrich)]

The meta-meta-bugs are making it difficult to track the individual pieces of work involved. If these bubble up as important pieces of data to track, file as individual pieces and make dependent on the main telemetry metabug (bug 671038).