Performance metrics for GeckoView streaming
Categories
(Core :: Performance, enhancement, P1)
Tracking
()
People
(Reporter: bdekoz, Assigned: bdekoz)
References
(Depends on 2 open bugs)
Details
Attachments
(2 files, 3 obsolete files)
6.65 KB,
text/plain
|
chutten
:
data-review+
|
Details |
47 bytes,
text/x-phabricator-request
|
Details | Review |
Exfiltrate a subset of existing telemetry probes for adequately defining page load from gecko telemetry to fenix/android using the new glean/geckoview_streaming approach.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
•
|
||
Hey Dexter, here is current state for the performance metrics.
Histograms.json
https://github.com/bdekoz/gecko/commit/f1a51aed317930358147d788a22d3030d05d77f1
metrics.yaml
https://github.com/bdekoz/gecko/commit/7a352fe25ee224cc4b105f1e68473627046a6a78
When I throw these into an arm64 build of Fenix nightly, and try to look at the pings, I'm not getting any joy.
See:
https://debug-ping-preview.firebaseapp.com/pings/performance-metrics
Any thoughts? I'm building nightly, and I tried Fenix.nightly and Fenix.performancetest binaries. Which seem like the right ones to test, aka nightly + telemetry enabled. When I scope about:support it looks like the right geckoview binaries are substituted.
But the metadata is pointing to this being the release channel, instead of nightly.
client_info/app_channel/release
If I can switch this, will the logged ping have the non_blank_paint metric?
Comment 3•5 years ago
|
||
For reference: https://github.com/mozilla/glean_parser/issues/95
Comment 4•5 years ago
|
||
(In reply to Benjamin De Kosnik [:bdekoz] from comment #2)
Any thoughts? I'm building nightly, and I tried Fenix.nightly and Fenix.performancetest binaries. Which seem like the right ones to test, aka nightly + telemetry enabled. When I scope about:support it looks like the right geckoview binaries are substituted.
Nothing looks wrong in the metrics files. I left a few comments there, but they are not responsible for metrics not showing up.
How are you making Android Components (and Fenix) use the GeckoView?
But the metadata is pointing to this being the release channel, instead of nightly.
client_info/app_channel/release
If I can switch this, will the logged ping have the non_blank_paint metric?
That's due to the way Fenix reports channel. It doesn't mean it's not using GeckoView nightly, but that it's using Fenix release. Should not be a problem, I think, as long as you're sure you're importing the right version of GeckoView.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 5•5 years ago
|
||
clearning the needinfo flag for the build questions, as Alessio worked through that part with me last week
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
Assignee | ||
Comment 7•5 years ago
|
||
WIP performance metrics exfiltration from GeckoView
Comment 8•5 years ago
|
||
Assignee | ||
Comment 9•5 years ago
•
|
||
Hey Chenxia, this is the data review with the changes that Chris requested. I believe that Histograms.json and metrics.yaml are now in sync, and that each metric now has an individual owner.
I also dropped two metrics that I'll add in a later patch: NETWORK_CACHE_SIZE and BFCACHE_PAGE_RESTORED.
Assignee | ||
Comment 10•5 years ago
|
||
Hi Chris, here are the changes you requested for the performance team metrics. I believe all the metrics now have both an individual owner, and are also pointed at the correct mailing list. (And that the performance team is actually monitoring this list....)
Comment 11•5 years ago
|
||
Assignee | ||
Comment 12•5 years ago
|
||
Assignee | ||
Comment 13•5 years ago
|
||
This looks ready to land so setting checkin-needed flag
Comment 14•5 years ago
|
||
Comment 15•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Updated•5 years ago
|
Description
•