Closed Bug 1580238 Opened 6 years ago Closed 6 years ago

Extend telemetry for QuotaManager initialization time

Categories

(Core :: Storage: Quota Manager, task, P2)

task

Tracking

()

RESOLVED FIXED
mozilla71
Tracking Status
firefox71 --- fixed

People

(Reporter: tt, Assigned: tt)

References

Details

Attachments

(3 files)

QM_REPOSITORIES_INITIALIZATION_TIME is recorded until the end of 71. We want to extend it, but we can also consider adjusting some parameters.

Now the high and n_bucket are:
"high": 30000,
"n_buckets": 30

Some initial suggestions from the team is that: changing "high": 120000, but keep the "n_buckets" as what it is now (30).
Also, we could consider extending the current one and adding another one so that we can compare that without querying by ourselves.

In short:
Option one: Make another probe (QM_REPOSITORIES_INITIALIZATION_TIME_V2) and with high 120000 and n_buckets 30
Option two: Extend the current one and make another probe as well

Note: Jan might give other feedback so ni him below

Flags: needinfo?(jvarga)

I think we should extend the existing probe since we are going to ship new features that affect the initialization time significantly and we want to be able to easily compare it with old releases. 3 releases should be enough I guess.

I also think we need a new probe, because we don't know what is the worst storage initialization time. We just know that there's around 2-3% of samples with init time > 30s. So going from 30s to 120s should be enough.

Not sure about n_buckets, but it seems 50 is used by most of the probes in Histograms.json.

Flags: needinfo?(jvarga)
Attachment #9092019 - Attachment description: Bug 1580238 - Extend the expired relase for the prob of initialization time on QM and add another one to catch the worst condition; → Bug 1580238 - Extend the release for the prob of initialization time on QM and add another one to catch the longest time;
Priority: -- → P2
Attachment #9092022 - Flags: data-review?(chutten) → data-review?(teon)
Comment on attachment 9092020 [details] Data-review for extending the QM_REPOSITORIES_INITIALIZATION_TIME Load-balancing to Teon.
Attachment #9092020 - Flags: data-review?(chutten) → data-review?(teon)
Comment on attachment 9092022 [details] Data-review for adding QM_REPOSITORIES_INITIALIZATION_TIME_V2 DATA COLLECTION REVIEW RESPONSE: Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate? Yes. This collection is Telemetry so is documented in its definitions file [Histograms.json](https://hg.mozilla.org/mozilla-central/file/tip/toolkit/components/telemetry/Histograms.json) and the [Probe Dictionary](https://telemetry.mozilla.org/probe-dictionary/). Is there a control mechanism that allows the user to turn the data collection on and off? Yes. This collection is Telemetry so can be controlled through Firefox's Preferences. If the request is for permanent data collection, is there someone who will monitor the data over time? No. This collection will expire in Fx 77. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under? Category 1, Technical. Is the data collection request for default-on or default-off? Default on for all channels. Does the instrumentation include the addition of any new identifiers? No. Is the data collection covered by the existing Firefox privacy notice? Yes. Does there need to be a check-in in the future to determine whether to renew the data? Yes. :ttung is responsible for renewing or removing the collection before it expires in Fx 77. --- Result: datareview
Attachment #9092022 - Flags: data-review?(teon) → data-review+

Hi Teon,

needinfo'ing, in the case of you accidentally missing the other data-review request for extending the existing telemetry.

Attachment #9092020 [details] is for extending the existing telemetry probe (QM_REPOSITORIES_INITIALIZATION_TIME). Please feel free to let me know if that doesn't need a data-review or I should put it on another bug, or something else. Thanks!

Flags: needinfo?(teon)
Comment on attachment 9092020 [details] Data-review for extending the QM_REPOSITORIES_INITIALIZATION_TIME DATA COLLECTION REVIEW RESPONSE: Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate? Yes. This collection is Telemetry so is documented in its definitions file [Histograms.json](https://hg.mozilla.org/mozilla-central/file/tip/toolkit/components/telemetry/Histograms.json) and the [Probe Dictionary](https://telemetry.mozilla.org/probe-dictionary/). Is there a control mechanism that allows the user to turn the data collection on and off? Yes. This collection is Telemetry so can be controlled through Firefox's Preferences. If the request is for permanent data collection, is there someone who will monitor the data over time? No. This collection will expire Fx 75. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under? Category 1, Technical. Is the data collection request for default-on or default-off? Default on for all channels. Does the instrumentation include the addition of any new identifiers? No. Is the data collection covered by the existing Firefox privacy notice? Yes. Does there need to be a check-in in the future to determine whether to renew the data? Yes. :ttung is responsible for renewing or removing the collection before it expires Fx 75. --- Result: datareview
Flags: needinfo?(teon)
Attachment #9092020 - Flags: data-review?(teon) → data-review+

(In reply to Tom Tung [:tt, :ttung] from comment #7)

Hi Teon,

needinfo'ing, in the case of you accidentally missing the other data-review request for extending the existing telemetry.

Attachment #9092020 [details] is for extending the existing telemetry probe (QM_REPOSITORIES_INITIALIZATION_TIME). Please feel free to let me know if that doesn't need a data-review or I should put it on another bug, or something else. Thanks!

thanks for the flag. completed both forgot to submit the second one yesterday

Pushed by shes050117@gmail.com: https://hg.mozilla.org/integration/autoland/rev/2d435f837f1c Extend the release for the prob of initialization time on QM and add another one to catch the longest time; r=janv,sg
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: