Closed Bug 1231708 Opened 4 years ago Closed 4 years ago

Verify the discarded ping size development

Categories

(Toolkit :: Telemetry, defect, P3)

defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox45 --- affected

People

(Reporter: gfritzsche, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [measurement:client])

We should do a run-down of the ping size developments since the more recent size optimizations.
I expect this to have greatly reduced the number of clients with overly big pings, as tracked via histograms:
TELEMETRY_DISCARDED_SEND_PINGS_SIZE_MB
TELEMETRY_DISCARDED_PENDING_PINGS_SIZE_MB

We should do a proper per-client breakdown of this and the size developments.
TELEMETRY_DISCARDED_SEND_PINGS_SIZE_MB:
The biggest spike was 39 submissions on release, so this seems to be a non-issue.

TELEMETRY_DISCARDED_PENDING_PINGS_SIZE_MB:
The biggest spike is 18 submissions on release.

The submission count graph on the evolution view for this shows nicely how Alessios ping size limits affected 43 and 44 positively:
http://mzl.la/1PdwcXF
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
Summary: Run an analysis of the discarded ping size development → Verify the discarded ping size development
You need to log in before you can comment on or make changes to this bug.