Measure perf impact of GeckoLoginStorageDelegate#onLoginFetch
Categories
(Firefox for Android :: History, task)
Tracking
()
People
(Reporter: cpeterson, Unassigned)
Details
From github: https://github.com/mozilla-mobile/android-components/issues/5531.
GV
LoginStorage.Delegate#onLoginFetchrequires a synchronous response, but retrieving that information requires unlocking and querying storage backed by a DB. This performance hit could be mitigated by changing the GV API to expect a Future, or potentially by doing some complex caching inLoginsStorage. Both of these options would require substantial work. First, we should measure the impact of the current solution (wrap the call in runBlocking) in order to determineAcceptance Criteria
- [ ] Add a probe to determine time spent in
GeckoLoginStorageDelegate#onLoginFetch- [ ] File a follow-up to analyze resulting telemetry and determine whether or not further work is required
┆Issue is synchronized with this Jira Task
Change performed by the Move to Bugzilla add-on.
Comment 1•3 years ago
|
||
The severity field is not set for this bug.
:cpeterson, could you have a look please?
For more information, please visit auto_nag documentation.
| Reporter | ||
Updated•3 years ago
|
Updated•3 years ago
|
Description
•