The default bug view has changed. See this FAQ.

Standardize max time for necko telemetry stats at 30 seconds, not 10

RESOLVED FIXED in mozilla9

Status

()

Core
Networking
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: jduell, Unassigned)

Tracking

unspecified
mozilla9
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Created attachment 559634 [details] [diff] [review]
fix max time of histograms at 30 sec

My personal browser's about:telemetry has a big spike in the max value of 10K for a lot of the HTTP/necko timings.  I.e there must be a long tail, but we're clamping the max at 10 sec and throwing everything higher in the 10K bucket.

(Maybe I should get a new ISP :) but that's another issue.)

This patch standardizes 30 secs as the max (some of our stats were already using 30 sec).

Note: the histograms don't seem to suffer visually from the larger limit in about:telemetry (the display logic gives a lot of granularity to the smaller end of the scale).  They don't look as good at the telemetry page, which uses linear graphs, but I still think they'd be ok:

  https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics&path=telemetry/&file=TelemetryHistogram.wcdf
Attachment #559634 - Flags: review?(honzab.moz)
Attachment #559634 - Flags: review?(honzab.moz) → review+
(Reporter)

Comment 1

6 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/087ff10b7a3c
Whiteboard: [inbound]
Target Milestone: --- → mozilla9
https://hg.mozilla.org/mozilla-central/rev/087ff10b7a3c
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Whiteboard: [inbound]
You need to log in before you can comment on or make changes to this bug.