Implement Fission analog of existing CONTENT_FRAME_TIME_VSYNC
Categories
(Core :: Performance: General, enhancement, P2)
Tracking
()
| Fission Milestone | M6 |
People
(Reporter: ccd, Unassigned)
References
Details
Attachments
(1 file)
|
2.09 KB,
text/plain
|
ccd
:
data-review+
|
Details |
The proposal is to create a analog of CONTENT_FRAME_TIME_VSYNC, that separates out the measurements of Fission and non-Fission windows.
The probe would return a nested histogram with keys corresponding to Fission, and non-Fission windows. The measurements are identical to those in the existing probe. The rationale is that it is possible for a user to have both Fission and non-Fission windows in the same session, and the need accurate Fission measurements requires this analog to obtain Fission specific measurements.
|
||
Comment 1•5 years ago
|
||
Would be nice to have for Fission dogfooding (M5)
|
|
||
Comment 2•5 years ago
|
||
Move Fission telemetry probe bugs from M5 dogfooding milestone to M6 Nightly.
|
|
||
Comment 3•5 years ago
|
||
WONTFIX because we don't need new Fission probe analogs for existing probes.
Based on WINDOW_REMOTE_SUBFRAMES_ENABLED_STATUS telemetry, less than 0.5% of windows in Fission sessions were non-Fission. That number is small enough that we don't need to worry about Fission users' non-Fission windows' telemetry polluting their Fission windows' telemetry.
Description
•