Decide on update agent task schedule (trigger)
Categories
(Toolkit :: Application Update, task, P3)
Tracking
()
People
(Reporter: agashlin, Unassigned)
References
(Blocks 1 open bug)
Details
We likely want a daily schedule for the update agent to check for updates, but we may want this to vary based on channel. I'd like to get some input on this from the releng perspective.
Daily
Windows Task Scheduler will run the task at a given time during the day, though it can be set to run the task later if it was missed. We need to pick a time of day, or decide how we will schedule the check based on the install time (12 hours later to likely end up in unused time?)
We can have a random delay to avoid everyone in a timezone hitting the update check at once).
Some points of reference from my machine:
- Google Update (Omaha) uses a daily or hourly schedule starting 5 minutes from the install time: https://github.com/google/omaha/blob/3061c8410a86115c4ff581799f2990b451a62c05/omaha/common/scheduled_task_utils.cc#L829
- Microsoft OneDrive is scheduled for 04:00 and 14:00 on my system, it uses an (up to) 1 hour random delay.
- Nvidia has stuff scheduled every 6 hours from 00:25
Logon / Boot
Do we want to run the task shortly after logon (for per-user accounts), or boot (for local service)? This would increase the likelihood of updating before Firefox runs, but:
- Running stuff at startup is going to hit when disk load is worst, and running an update then could make things yet worse.
- With Firefox now starting automatically on Windows 10 in many cases, the update agent likely won't even get a chance to run anyway.
Google Update and Nvidia have an "at log on of any user" trigger.
Idle, batteries, network
There is a mechanism to only run the task if the system is idle, but I don't know much about how this works. Details here. Omaha doesn't bother with it; OneDrive uses the related setting to "Stop if the computer ceases to be idle". Generally I'm not big on the idea of stopping the task from Task Scheduler.
We can decide not to start the task if the machine is on batteries, and to stop if it goes on batteries.
We could also not start unless a network is available, which may be desired.
|
||
Updated•5 years ago
|
|
Reporter | |
Comment 1•4 years ago
|
||
In the bug 1515451 patch currently up for review, the schedule is set to once per 24 hours (starting 24 hours from the first registration of the task), and if that is missed (due to e.g. the computer being shut down), the task will run whenever it is next possible to do so.
|
||
Comment 2•3 years ago
|
||
The background update task runs, by default, every 7 hours.
Description
•