1615369 - Performance metrics Round 2 for GeckoView streaming

Status: RESOLVED FIXED

(Core :: Performance: General, enhancement, P1)

Description

[Benjamin De Kosnik [:bdekoz]]

Exfiltrate an additional subset subset of existing telemetry probes for adequately defining page load from gecko telemetry to fenix/android using the new glean/geckoview_streaming approach. This fills in holes and builds on first set of metrics that landed in BZ 1580077.

The known holes in existing datasets are:

Network
network page weight/total bytes downloaded
time to first network idle
redirects
reloads/redirect

Startup/Navigation
cold warm startup
F/B cache

Memory
system memory total
current resident set size for Mozilla apps

Environment
system cpu count
system cpu speed
system memory size
system disk cache size

Potentially useful metrics, but not necessarily a requirement for this round of work:

Resources (layout and necko)
how many images
how many flex boxes
how many reflows
if/how was stuff pushed out of cache (css forced out by video)

FXA sync
time to migration for
passwords
bookmarks
history
how many tabs are sent from desktop for mobile

Media playback
resolution of video file (not a fixed number, can change)
has resolution changed within playback
average frame rage
size
playback minutes
if CDN?
“time to transfer from CDN”
stalls, want to decode video and audio but don’t have data yet
if user initiated or autoplay
if subtitiles

New metrics relative to responseStart
relPageLoadTime
relDomInteractiveTime
relDomContentLoadedTime

Comment 1

[Andrew Creskey [:acreskey]]

For pageload, I think it would be valuable to know where the navigation originated from.

e.g.
-cold process applink (i.e. the gecko process had been killed by the OS or user)
-warm process applink (gecko process was already running)
-url bar entry
-link selection from document
-history or similar selection
-refresh
-custom tabs
-?

Comment 2

[Benjamin De Kosnik [:bdekoz]]

Attachment: data_review.1615369.md

Comment 3

[Benjamin De Kosnik [:bdekoz]]

Feedback from round one is that network was mostly right, Dragana suggested these two addtions. The real issue is that there is no engagment info, so fixing this is the focus of this round.

Comment 4

[Benjamin De Kosnik [:bdekoz]]

Attachment: Bug 1615369 - Performance metrics Round 2 for GeckoView streaming. r=dexter

Comment 5

[Chris H-C :chutten]

Comment on attachment 9159853 [details]
data_review.1615369.md

Are all of these recorded in parts of the codebase that makes up engine-gecko? `browser.engagement.active_ticks` for example is recorded in TelemetrySession.jsm which I believe not only isn't run in geckoview, but isn't present.

Comment 6

[Benjamin De Kosnik [:bdekoz]]

Agh, hang on with this patch, sorry double checking with data sci but delayed.

Comment 7

[Chris H-C :chutten]

Comment on attachment 9159853 [details]
data_review.1615369.md

Clearing data reviews while conversations are pending.

Comment 8

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Triage: Benjamin, is this still needed? If not, we were wondering if this should be closed.

Comment 9

[Benjamin De Kosnik [:bdekoz]]

Closing, metric shaping went other ways.