Last Comment Bug 686067 - Standardize max time for necko telemetry stats at 30 seconds, not 10
: Standardize max time for necko telemetry stats at 30 seconds, not 10
Product: Core
Classification: Components
Component: Networking (show other bugs)
: unspecified
: All All
: -- normal (vote)
: mozilla9
Assigned To: Nobody; OK to take it and work on it
: Patrick McManus [:mcmanus]
Depends on:
Blocks: 650129
  Show dependency treegraph
Reported: 2011-09-09 17:26 PDT by Jason Duell [:jduell] (needinfo me)
Modified: 2011-09-16 07:29 PDT (History)
2 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

fix max time of histograms at 30 sec (2.33 KB, patch)
2011-09-09 17:26 PDT, Jason Duell [:jduell] (needinfo me)
honzab.moz: review+
Details | Diff | Splinter Review

Description User image Jason Duell [:jduell] (needinfo me) 2011-09-09 17:26:20 PDT
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:
Comment 1 User image Jason Duell [:jduell] (needinfo me) 2011-09-15 18:21:19 PDT
Comment 2 User image :Ehsan Akhgari (in Taipei, laggy response time) 2011-09-16 07:29:11 PDT

Note You need to log in before you can comment on or make changes to this bug.