Audit telemetry probes for memory usage
Categories
(Core :: Graphics: WebRender, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: kats, Assigned: kats)
References
Details
Attachments
(2 files)
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/plain
|
chutten
:
data-review+
|
Details |
Turns out there are some telemetry probes that record memory usage in Firefox:
MEMORY_RESIDENT_FAST
MEMORY_UNIQUE
MEMORY_TOTAL
MEMORY_VSIZE
.. and other less useful-looking ones
erahm says that adding resident-peak would be easyish to add as well since we have that in about:memory and it's easy to grab.
We should check that the numbers provided by these are useful on Android (and GeckoView in particular), and that we can use these probes to compare WR on vs WR off.
Assignee | ||
Comment 1•5 years ago
|
||
I looked at the telemetry data for Fennec for these probes and they seem sane. The data is collected for main and content processes which isn't relevant for Fennec but will be fine for GeckoView (AFAIK we're not planning on enabling a GPU process on GeckoView). I also think we should record the peak resident memory as it gives us a better view of memory usage over time as opposed to the instantaneous memory usage whenever the snapshot was taken. The implementation of that uses the getrusage
linux API which should work on android, so I don't foresee any problems with adding that to the list. I'm building a patch to do that.
Assignee | ||
Comment 2•5 years ago
|
||
Assignee | ||
Comment 3•5 years ago
|
||
Comment 4•5 years ago
|
||
Comment 6•5 years ago
|
||
bugherder |
Description
•