GV should disable logging by default in opt GV builds
Categories
(GeckoView :: General, defect, P3)
Tracking
(Performance Impact:low, firefox69 wontfix, firefox70 fix-optional, firefox71 affected)
Performance Impact | low |
Tracking | Status | |
---|---|---|
firefox69 | --- | wontfix |
firefox70 | --- | fix-optional |
firefox71 | --- | affected |
People
(Reporter: smaug, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: perf:pageload)
instagram on G5 through geckoview nightly from taskcluster
https://perfht.ml/2ML5Zc5
Looks like most of it is logging, and 21ms per navigation doesn't seem too bad to me anyway.
Reporter | ||
Comment 2•5 years ago
|
||
21ms is rather bad (when one of the key goals is Fenix page load performance) but not p1 bad.
Comment 3•5 years ago
|
||
GV should enable logging by default in debug builds for the benefit of GV developers. See debugLogging
API bug 1573304 to control logging.
I filed a Fenix issue asking them to call debugLogging
appropriately, since GV can't know at runtime whether the app is a debug or opt build: https://github.com/mozilla-mobile/fenix/issues/4763
Updated•5 years ago
|
Updated•5 years ago
|
Comment 4•5 years ago
|
||
Fenix just landed code to disable GV logging in their release builds, but we should still fix GV's default for the benefit of other GV-powered apps like FxR.
https://github.com/mozilla-mobile/fenix/commit/eb26d951ab525e510c386ef8d15068dc5fa04e0f
Updated•5 years ago
|
Updated•5 years ago
|
Updated•3 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Description
•