Closed Bug 969252 Opened 6 years ago Closed 5 years ago

Fennec has used 3.29GB since enabling FxA authenticated sync (in ~2days)

Categories

(Firefox for Android :: Android Sync, defect, major)

ARM
Android
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: blassey, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: meta)

Attachments

(2 files)

This is more than an order of magnitude increase over normal usage.
I'm assuming this is network bandwidth.  It's feasible, I suppose -- all those unthrottled network requests.
Either token fetches are super expensive, or syncs aren't finishing, so you're doing a full first time Sync every 30 seconds. 

adb log, please.
tracking-fennec: ? → 29+
Component: FxA → Android Sync
Flags: needinfo?(blassey.bugs)
OS: Mac OS X → Android
Product: Firefox for Android → Android Background Services
Hardware: x86 → ARM
Version: Trunk → unspecified
(In reply to Richard Newman [:rnewman] from comment #2)
> Either token fetches are super expensive, or syncs aren't finishing, so
> you're doing a full first time Sync every 30 seconds. 
> 
> adb log, please.

Any particular tag?
Flags: needinfo?(blassey.bugs)
(In reply to Brad Lassey [:blassey] (use needinfo?) from comment #3)
> (In reply to Richard Newman [:rnewman] from comment #2)
> > Either token fetches are super expensive, or syncs aren't finishing, so
> > you're doing a full first time Sync every 30 seconds. 

Oh, yeah, failed first sync is way more likely.

> > adb log, please.
> 
> Any particular tag?

FxSync, FxAccounts.
Severity: normal → major
Depends on: 971972
needinfo on Brad to toss up a log
Flags: needinfo?(blassey.bugs)
I think we've already got a working theory, which is why this is depending on bug 971972
Flags: needinfo?(blassey.bugs)
Attached file sync.log
I'm still experiencing high data and battery use (73% of battery usage) with sync enabled.
Attachment #8389951 - Attachment mime type: text/x-log → text/plain
Depends on: 982782
Attached file fxaccount log
I setup FxAccount / Sync on a new Nexus 5 running Nightly, then let the phone sleep. In the morning, Nightly had used 39% of the battery. 

I setup Sync to pull bookmarks, passwords and tabs. The data appeared to be on my phone.

I am attaching a log in case the 39% battery usage could be reduced.
(In reply to Mark Finkle (:mfinkle) from comment #8)

> I setup FxAccount / Sync on a new Nexus 5 running Nightly, then let the
> phone sleep. In the morning, Nightly had used 39% of the battery. 

A logcat with times (adb logcat -v time) would be handy: we can see that we're syncing every half hour, but not how long the sync is taking.

Half an hour might be too aggressive, if nothing else on the device is live — it'll be preventing sleep and waking the network stack sixteen times overnight.

If we decide to tweak that, we need to consider the impact on perceived readiness and first-run behavior: Android will schedule a sync when the DBs get touched on launch, which is both a good thing (no need for periodic syncs!) and a bad thing (now we're doing a sync while you're trying to browse).
Depends on: 984723
Depends on: 836780
nalexander, you got the bug number in your pull request wrong -- Bug 836790, not Bug 836780. :)
Depends on: 836790
No longer depends on: 836780
Keywords: meta
tracking-fennec: 29+ → ---
I think things have come a long way in the last year, and keeping this open won't fix the remainder on its own.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
Product: Android Background Services → Firefox for Android
You need to log in before you can comment on or make changes to this bug.