Handling input signals in the browser process for global scheduling decision

[Alexander Timin]

Hi Tim, Dave & input-team, 

We (scheduling & GRC teams) recently started a discussion around global scheduler — having a global policy making logic in the browser process (preliminary design doc). One of the goals of this project is a global handling of user gestures (e.g. stopping all background tabs during a user gesture).

I would like to hear your thoughts about this. In particular, I have a very rough idea of the global architecture of input handling, in particular the interactions between the browser process, the main thread and the compositor thread, especially with new scrolling initiatives coming. I would appreciate if you could share some design docs around this or walk me through.

Thanks,

Alexander

[Daniel Cheng]

On Fri, Sep 1, 2017, 04:10 Alexander Timin <alt...@chromium.org> wrote:

Hi Tim, Dave & input-team, 

We (scheduling & GRC teams) recently started a discussion around global scheduler — having a global policy making logic in the browser process (preliminary design doc). One of the goals of this project is a global handling of user gestures (e.g. stopping all background tabs during a user gesture).

Sorry, I'm not familiar with this: what does it mean to stop all background tabs?

Daniel

I would like to hear your thoughts about this. In particular, I have a very rough idea of the global architecture of input handling, in particular the interactions between the browser process, the main thread and the compositor thread, especially with new scrolling initiatives coming. I would appreciate if you could share some design docs around this or walk me through.

Thanks,

Alexander

--
You received this message because you are subscribed to the Google Groups "scheduler-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scheduler-de...@chromium.org.
To post to this group, send email to schedu...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/scheduler-dev/CALHg4n%3DmL_zPZFx4SaEh6Zk602TmGzTEOnLz4e7rBZVSFHLxFA%40mail.gmail.com.

[Alexander Timin]

On 12 September 2017 at 17:28, Daniel Cheng <dch...@chromium.org> wrote:

On Fri, Sep 1, 2017, 04:10 Alexander Timin <alt...@chromium.org> wrote:

Hi Tim, Dave & input-team, 

We (scheduling & GRC teams) recently started a discussion around global scheduler — having a global policy making logic in the browser process (preliminary design doc). One of the goals of this project is a global handling of user gestures (e.g. stopping all background tabs during a user gesture).

Sorry, I'm not familiar with this: what does it mean to stop all background tabs?

 

In this context it means that we want to completely stop running tasks like timers in background tabs during a user gesture to reduce total load on the system and ensure that nothing gets descheduled.

 

Daniel

I would like to hear your thoughts about this. In particular, I have a very rough idea of the global architecture of input handling, in particular the interactions between the browser process, the main thread and the compositor thread, especially with new scrolling initiatives coming. I would appreciate if you could share some design docs around this or walk me through.

Thanks,

Alexander

--
You received this message because you are subscribed to the Google Groups "scheduler-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to scheduler-dev+unsubscribe@chromium.org.