Closed Bug 1214620 Opened 9 years ago Closed 9 years ago

Measure the impact of the number of thread hangs on the ping size

Categories

(Toolkit :: Telemetry, defect, P3)

Product:
Toolkit
Component:
Telemetry
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox42 --- wontfix
firefox43 --- affected
firefox44 --- affected

People

(Reporter: Dexter, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [unifiedTelemetry][measurement:client])

We need to understand the impact of the number of thread hangs reported by Telemetry on the average ping size. This could drive further Telemetry optimizations: if in-memory costs are acceptable, we could keep the hangs in memory and make them available through about:telemetry, while only sending N of them along with the pings.
Priority: -- → P3
Whiteboard: [unifiedTelemetry][measurement:client]
Blocks: 1220718
No longer blocks: 1186986
We will investigate ping size in Q1 again, but we should drive this from a top-down view. We will run analysis to see which top sections impact size heavily and file further bugs from there.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.