Open Bug 1796417 Opened 3 years ago Updated 3 years ago

Measure perf impact of GeckoLoginStorageDelegate#onLoginFetch

Categories

(Firefox for Android :: History, task)

All
Android
task

Tracking

()

People

(Reporter: cpeterson, Unassigned)

Details

From github: https://github.com/mozilla-mobile/android-components/issues/5531.

GV LoginStorage.Delegate#onLoginFetch requires 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 in LoginsStorage. 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 determine

Acceptance 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.

The severity field is not set for this bug.
:cpeterson, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(cpeterson)
Severity: -- → N/A
Type: defect → task
Flags: needinfo?(cpeterson)
You need to log in before you can comment on or make changes to this bug.