Closed
Bug 762682
Opened 12 years ago
Closed 9 years ago
Provide data normalization for older data, fit new data based on adoption rates
Categories
(Mozilla Metrics :: Frontend Reports, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Moved to JIRA
People
(Reporter: taras.mozilla, Unassigned)
References
Details
(Whiteboard: [JIRA STATMOD-21] [Telemetry] -- needs PM project priority)
Please add a 'fancy stat data-fitting' view to telemetry evolution to complement the current 'raw' view. Telemetry evolution is the most useful telemetry dashboard. It reports builds by build id and lets us see trends. The main use for this dashboard is to see regressions, optimizations in the field. Over the past week multiple developers said telemetry would be significantly more useful if it tried to deal with noise in the data. 1) Normalization for older data(ie data over 2 weeks old?): Unfortunately due to variations in daily usage patterns there is fair bit of noise. Would be great to have a 'normalize' mode to turn daily swings into a straight line. 2) Use an adoption curve to plot new data. It takes about a week to stabilize on the number of reports from a particular build. As of today build from 12-06-01 seems to have been adopted and left behind(ie the number of submissions from that build is not going to increase much in the future). Since early adopters have different performance patterns for later adopters, we could not reliably use this datapoint until today. Would have been useful to have telemetry evolution predict where that point was going to end up based on previous data.
Comment 1•12 years ago
|
||
Marking: in group of > 33 asks for Telemetry that need PM priority before triage/scheduling.
Status: NEW → ASSIGNED
Whiteboard: Telemetry -- needs PM project priority
Comment 3•12 years ago
|
||
https://metrics.mozilla.com/projects/browse/METRICS-995
Target Milestone: Backlogged - BZ → Targeted - JIRA
Updated•12 years ago
|
Whiteboard: Telemetry -- needs PM project priority → [JIRA STATMOD-21] Telemetry -- needs PM project priority
Comment 4•12 years ago
|
||
Comment made: https://metrics.mozilla.com/projects/browse/STATMOD-21
Reporter | ||
Comment 5•12 years ago
|
||
(In reply to Saptarshi Guha from comment #4) > Comment made: https://metrics.mozilla.com/projects/browse/STATMOD-21 for 1) See https://metrics.mozilla.com/data/content/pentaho-cdf-dd/Render?solution=metrics2&path=%2Ftelemetry&file=telemetryEvolution.wcdf&bookmarkState={%22impl%22%3A%22client%22%2C%22params%22%3A{%22referenceDate%22%3A%222012-10-03%22%2C%22appNameParameter%22%3A%22[Application].[Firefox]%22%2C%22osParameter%22%3A%22[OS].[WINNT]%22%2C%22channelParameter%22%3A%22[Channel].[nightly]%22%2C%22reasonParameter%22%3A%22[Reason].[idle-daily]%22%2C%22histogramParameter%22%3A%22[Histogram].[MEMORY_RESIDENT]%22%2C%22histogramPopupTools%22%3A%22%22%2C%22duplicateHistogram%22%3A%22%23duplicateHistogram%22%2C%22medianButtonParam%22%3A0%2C%22scatterChart%22%3A%22%22}} The data shows periodic swings. That's not completely 'amazingly stable after 7 days'. This makes it hard to see if it's trending in any particular direction.
Updated•11 years ago
|
Whiteboard: [JIRA STATMOD-21] Telemetry -- needs PM project priority → [JIRA STATMOD-21] [Telemetry] -- needs PM project priority
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•