1741759 - CONTENT_PROCESS_MAX (and PRECISE) mistakenly use a histogram instead of a scalar

Status: RESOLVED FIXED

(Core :: DOM: Content Processes, defect, P2)

Description

[Randell Jesup [:jesup] (needinfo me)]

CONTENT_PROCESS_MAX (and the PRECISE variant) use a Histogram instead of a Scalar. This means that if you have 20 content processes, you'll get telemetry values of 3, 4, 5, 6, 7, etc up to 20 - each time we call Telemetry::Accumulate() we add another entry to the outgoing telemetry. Scalars will just send the final value given to ::ScalarSet().

This means the current telemetry is hard-to-impossible to use. It is possible to untangle the data from what we store in sql, but not from the current dashboards.

We should replace it with a new Scalar value.

Comment 1

[Randell Jesup [:jesup] (needinfo me)]

Attachment: Bug 1741759 - Make CONTENT_PROCESS_MAX/etc scalars instead of histograms r=chutten

We want to record one max value per (sub)session

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/58c1a5993ec4
Make CONTENT_PROCESS_MAX/etc scalars instead of histograms r=chutten

Comment 3

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/58c1a5993ec4