741042 - Add telemetry support for timing XUL profile import

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: General, defect)

Description

[Mark Finkle (:mfinkle) (use needinfo?)]

We'd like to get an idea of how time consuming the XUL profile import can be on various devices and profile sizes.

Comment 1

[Gian-Carlo Pascutto [:gcp]]

We do not have Telemetry support in Java, do we?

Comment 2

[Gian-Carlo Pascutto [:gcp]]

Attachment: Patch 1. Telemetry for XUL profile migration

This collects the statistics from the XUL profile. It adds one extra query to get the amount of history entries, but the overhead of that seems to be negligible.

The question is if we will ever get any of this Telemetry, given that Telemetry doesn't send on every startup for every user, *and* we only collect this once. From what I understood from Taras, Telemetry is persistent now and requires the following to work:

a) shutdown firefox cleanly
b) have the user opt in
c) have telemetry turn on subsequent start and not have persistent data from before overwritten

I'm not sure what (c) means exactly, but I think that as we never overwrite these values (except potentially history count, but then its always with the same value!), they will be kept in sessionHistograms.dat.4little and will get sent if Telemetry ever decides to send its stuff.

Do we save and persist Telemetry if the user hasn't opted in yet?

Comment 3

[Gian-Carlo Pascutto [:gcp]]

Pushed with description fixes.

https://hg.mozilla.org/integration/mozilla-inbound/rev/89e69819fa98
https://hg.mozilla.org/integration/mozilla-inbound/rev/d5bc02349369

Comment 4

[Marco Bonardo [:mak]]

https://hg.mozilla.org/mozilla-central/rev/89e69819fa98
https://hg.mozilla.org/mozilla-central/rev/d5bc02349369