Closed Bug 1454031 Opened 6 years ago Closed 6 years ago

Un-expire CONTENT_PROCESS_LAUNCH_TIME_MS probe

Categories

(Toolkit :: Telemetry, enhancement)

All
Unspecified
enhancement
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla61
Tracking Status
firefox61 --- fixed

People

(Reporter: Felipe, Assigned: Felipe)

Details

Attachments

(1 file)

The telemetry probe CONTENT_PROCESS_LAUNCH_TIME_MS has been expired since Firefox 57, but content process launch time is something that we'll be focusing again, specially with Project Fission in mind. So it'll be useful to measure this again over time.

The last version to be in central during this year will be 66, so I propose we re-enable this probe until that version, which will give us plenty of time to use the probe and re-evaluate if it needs to continue to be watched next year.

(Note: "expires_in_version" marks the first version in which the probe expires, so I'll set it to 67, in order to cover 66)
---- 1 - What questions will you answer with this data?

We want to track the launch time of content processes over time, and hopefully see improvements made to it

---- 2 - Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements? Some example responses:

Yes, direct benefit for users, as an important performance aspect, specially in light of Project Fission.

---- 3 - What alternative methods did you consider to answer these questions? Why were they not sufficient?

Talos numbers will also be used on this effort, but real-world data is very valuable

---- 4 - Can current instrumentation answer these questions?

Yes

---- 5 - List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the Mozilla wiki.

CONTENT_PROCESS_LAUNCH_TIME_MS: Technical Data

---- 6 - How long will this data be collected? Choose one of the following:

During this year, potentially renewable. Explanation in comment 0.

---- 7 - What populations will you measure?

All users and channels

---- 8 - If this data collection is default on, what is the opt-out mechanism for users?

Opting out of telemetry

---- 9 - Please provide a general description of how you will analyze this data.

Looking at the telemetry dashboard and evolution

---- 10 - Where do you intend to share the results of your analysis?

With the team that I'm part of, which is focusing on performance improvements
Comment on attachment 8967807 [details]
Bug 1454031 - Un-expire CONTENT_PROCESS_LAUNCH_TIME_MS probe.  data-review=chutten DONTBUILD

https://reviewboard.mozilla.org/r/236482/#review242316
Attachment #8967807 - Flags: review?(chutten) → review+
Pushed by felipc@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/c84333b1cc67
Un-expire CONTENT_PROCESS_LAUNCH_TIME_MS probe. r=chutten data-review=chutten DONTBUILD
https://hg.mozilla.org/mozilla-central/rev/c84333b1cc67
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
You need to log in before you can comment on or make changes to this bug.