64
edits
QA/Sync/Client/Sync Timers: Difference between revisions
added "services.sync.scheduler.activeInterval" variable info
(Created page with "{{draft}} = Purpose = * A high level light weight document to explain client syncing timers/schedulers * This document is not intended as guide for planning or development. It i...") |
(added "services.sync.scheduler.activeInterval" variable info) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= Purpose = | = Purpose = | ||
* A high level light weight document to explain client syncing timers/schedulers | * A high level light weight document to explain client syncing timers/schedulers | ||
| Line 30: | Line 28: | ||
= Sync Client Timers and Schedulers = | = Sync Client Timers and Schedulers = | ||
The Sync client has | The Sync client has a configuration, found in about:config, that controls "how often" syncs are triggered. Below is that configuration and how it affects Syncs timing behavior. | ||
<!-- | |||
== services.sync.scheduler.singleDeviceInterval == | == services.sync.scheduler.singleDeviceInterval == | ||
This config is followed only for sync accounts that have a single device connected. | This config is followed only for sync accounts that have a single device connected. | ||
| Line 43: | Line 41: | ||
* value = 90 seconds | * value = 90 seconds | ||
* client behavior - Whenever a new item is synced to a client (from the cloud/other client), the next sync will occur in 90 seconds. | * client behavior - Whenever a new item is synced to a client (from the cloud/other client), the next sync will occur in 90 seconds. | ||
--> | |||
== services.sync.scheduler.activeInterval == | |||
* value = 600 seconds (10 minutes) | |||
* value may be edited to a custom value of choice | |||
== services.sync. | == services.sync.syncInterval == | ||
* value = 600 seconds (10 minutes) | * value = 600 seconds (10 minutes) | ||
* client behavior - If the user is active (meaning user is browsing, but not triggering instant syncs or crossing score threshold), then next sync will occur in 10 minutes | * client behavior - If the user is active (meaning user is browsing, but not triggering instant syncs or crossing score threshold), then next sync will occur in 10 minutes | ||
== services.sync.syncThreshold == | |||
* | |||
* | |||
<!-- | |||
== services.sync.scheduler.idleTime == | == services.sync.scheduler.idleTime == | ||
* value = 300 seconds (5 minutes) | * value = 300 seconds (5 minutes) | ||
| Line 54: | Line 60: | ||
== services.sync.scheduler.idleInterval == | == services.sync.scheduler.idleInterval == | ||
* value = 3600 seconds (1 hour) | * value = 3600 seconds (1 hour) | ||
* client behavior - if the user becomes idle, as in above idleTime, the next sync occurs in one hour from time of becoming idle. | * client behavior - if the user becomes idle, as in above idleTime, the next sync occurs in one hour from time of becoming idle. --> | ||
Notes | |||
== Notes == | |||
* Returning from idle will trigger an instant sync. | * Returning from idle will trigger an instant sync. | ||