Closed
Bug 517597
Opened 16 years ago
Closed 16 years ago
waste fewer resources while a user only has one client active
Categories
(Firefox :: Sync, defect, P1)
Firefox
Sync
Tracking
()
RESOLVED
FIXED
0.7
People
(Reporter: mconnor, Assigned: mconnor)
References
Details
Attachments
(1 file, 2 obsolete files)
10.86 KB,
patch
|
Details | Diff | Splinter Review |
POC patch attached, default to 24 hours between syncs for users with a single client.
With this we'll sync after each startup, and then either manually or every 24 hours after that. Manual syncs will bump the next sync to 24 hours out from then.
To do/consider:
* Store next sync time as a pref, enforce 24 hours or manual syncs across restarts.
* Look at tracker-based sync calls to determine.
* Disable tab sync with a single client active.
Flags: blocking-weave1.0+
Assignee | ||
Comment 1•16 years ago
|
||
What this does:
* default sync interval for single-client users is 24 hours. Manual syncs are allowed in this case.
* scheduling works across sessions for all users (this helps with backoff too)
* We only sync on startup if we're past the next scheduled sync time.
* Tabs are not synced when there is a single client active.
Attachment #401553 -
Attachment is obsolete: true
Attachment #401788 -
Flags: review?(thunder)
Assignee | ||
Comment 2•16 years ago
|
||
This patch is on top of bug 518075, and there's a bit of cleanup for that yet.
This moves the consts to constants.js, and defines thresholds and intervals for different client modes. Basically, single-client should remain unchanged, but multi-client without mobile clients will have.
Attachment #401788 -
Attachment is obsolete: true
Attachment #401788 -
Flags: review?(thunder)
Comment 3•16 years ago
|
||
http://hg.mozilla.org/labs/weave/rev/98757a88f66c
Adjust how often Weave syncs based on the number of clients and only sync tabs if there are multiple clients.
Updated•7 years ago
|
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in
before you can comment on or make changes to this bug.
Description
•