Closed
Bug 1315981
Opened 9 years ago
Closed 9 years ago
t.m.o submission by build_id dropoff since Nov 2nd 2016
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mconley, Assigned: frank)
Details
Open up telemetry.mozilla.org, and look at a metric of your choice for Nightly, and make sure to chart by build_id on the X axis.
There's a noticeable dropoff in submission on Nov 2nd, and it hasn't recovered yet. According to chutten's Telemetry-based crash dashboard, the measurement of kuh (1000 usage hours) hasn't changed... so I'm placing my bet on pipline to t.m.o.
Here's an example chart:
https://mzl.la/2eAmVxh
| Reporter | ||
Comment 1•9 years ago
|
||
Here's chutten's Telemetry-based crash dashboard, for reference: https://chutten.github.io/telemetry_crashes/
| Reporter | ||
Comment 2•9 years ago
|
||
Also, the drop off is by about 50%, from the probes I've been looking at.
| Reporter | ||
Comment 3•9 years ago
|
||
Actually, one thing to note is that if you plot the graph with the submission date along the X axis, there's no drop-off.
So perhaps this is an update saturation problem.
| Assignee | ||
Updated•9 years ago
|
Assignee: nobody → fbertsch
Comment 4•9 years ago
|
||
Here's what I did: https://gist.github.com/chutten/3ac71bc6fde892eaf489337394dfaf84
There may have been a similar sort of effect last month, but it isn't as obvious as this month's. More analysis likely needed.
| Assignee | ||
Comment 5•9 years ago
|
||
Went ahead and looked at the distribution Submission Date - Build Date. Caution, these queries have NOT been reviewed.
The first [0] just takes all the nightly data and plots the distribution. It didn't seem as skewed left as I would have supposed, so I unweighted the users (i.e. each ping is only "worth" 1/count(pings), rather than all weighted equally - this weight heavy users don't skew results). That is available in [1]. It did move the 50th percentile a bit left, but not much effect other than that.
These results seem a bit surprising to me, it takes about a month before we see 50% of pings for a nightly build.
[0] https://sql.telemetry.mozilla.org/queries/1619/source#2870
[1] https://sql.telemetry.mozilla.org/queries/1622/source#2872
Comment 6•9 years ago
|
||
We get a full third of pings within two days, generally speaking, which is neat.
This is an average over all pings, I presume? I wonder if there are effects that move a given build's curve left or right...
| Assignee | ||
Comment 8•9 years ago
|
||
Yes, we'll keep an eye on this, but seems to be okay for now.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(fbertsch)
Resolution: --- → WORKSFORME
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•