Re: [Task Scheduler] scheduling flexibility

On Tue, Nov 5, 2013 at 3:35 PM, Michael van Ouwerkerk
<mvanouwerkerk@chromium.org> wrote:
> How do people feel about allowing for scheduling flexibility in the Task
> Scheduler API? The goal of this feature would be to save battery power. If
> the system has flexibility about when to precisely run a task, it could
> batch multiple tasks together, or only run tasks when the device is awake.
> This way, we could avoid waking up devices too frequently.
>
> Some use cases require precise scheduling e.g. an alarm in the morning, or a
> cooking timer. But there are many tasks that are much less time sensitive,
> these could be scheduled flexibly e.g. syncing a news feed or auto-updating
> to a new version.
>
> Any comments? My apologies if this issue has been discussed previously.
>
> Regards,
>
> Michael van Ouwerkerk
>

Valid point. In my view, the use case could be formulated like this:
- a given platform or device policy / setting may support "scheduling
heartbeat" (similar to IP heartbeat)
- applications should have means to tell the user agent if they can
tolerate small delays (and how much. in terms of lower bound, desired,
upper bound) in task scheduling, let's call this "request"
- the user agent should have means to tell the application the
"response" about whether it can respect the request or not, or if it
can respect it with changes in requested max delay. The app can then
adapt to this.

That would mean introducing a function call (with the range expressed
as parameters), and a new event (with actual max delay as parameter).

Regards,
Zoltan

Received on Tuesday, 5 November 2013 14:44:21 UTC