Closed Bug 1013935 Opened 6 years ago Closed 4 months ago

Add telemetry to track the performance of Login Manager initialization

Categories

(Toolkit :: Password Manager, defect, P5)

defect

Tracking

()

RESOLVED INACTIVE

People

(Reporter: Paolo, Unassigned)

References

Details

(Whiteboard: [passwords:telemetry])

From bug 853549 comment 83:

::: browser/base/content/browser.js
@@ +1109,5 @@
> +        Services.logins;
> +      } catch (ex) {
> +        Cu.reportError(ex);
> +      }
> +    }, 3000);

It would be interesting to add some simple telemetry probes to see how effective this is. Ideas:

* What percentage of the time do we successfully do any async init (vs it being interrupted by a sync init)?
* What is the time distribution (in seconds after browser-startup) for when the first password manager call is made?
* When a sync-init occurs, how long does it take? (Ditto for async, just out of curiosity.)

This would help us know if 3 seconds is a good value or not, and if the sync-init is still a significant source of jank or not.
This bug looks easy and valuable enough to be put in the Firefox backlog.
Flags: firefox-backlog+
Can you provide some more information required to complete this task?
Flags: needinfo?(paolo.mozmail)
Matt, we were thinking of making this a good first bug and therefore add details on how to do it, but I'm not sure anymore whether we still want it or not. Since you're doing Logins work right now, deferring this to you.
Flags: needinfo?(paolo.mozmail)
Flags: needinfo?(MattN+bmo)
Flags: firefox-backlog+
Whiteboard: [passwords:telemetry]
Priority: -- → P5
Flags: needinfo?(MattN+bmo)

We're likely to switch the Rust logins backend before implementing this.

Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.