Call for volunteers: Finishing the per-frame scheduler

[Kentaro Hara]

Hi

As you may know, we've been migrating all tasks/timers from a per-renderer scheduler to a per-frame scheduler. The per-frame scheduler enables us to flexibly schedule tasks/timers per frame. For example, it enables to throttle offscreen iframes, which is a key technology to save power and improve responsiveness of the main frame.

To complete the migration, we need to migrate ~100 timers. ...so we might want to get some help from the community :D

(if you're interested in, please keep reading.)

The migration step is easy:

1) Pick up a timer from this sheet.

2) Basically, you just need to replace Timer<> with TaskRunnerTimer<> (example CL). The only non-trivial part is to understand the spec and choose a correct TaskType.

3) Upload a CL with BUG=624694. haraken@ is happy to review the patches.

Thanks!

--

Kentaro Hara, Tokyo, Japan

[Kentaro Hara]

Thanks all for contributing to moving tasks to the per-frame scheduler! We're currently 70% done :D

Note: Some people showed concern that the task migration may break websites because the per-frame scheduler is throttled in background tabs. To mitigate the concern, we mapped almost all DOM tasks to an unthrottled task runner at the moment. We'll move them back to the throttled task runner once the issues of the background throttling are resolved. i.e., the task migration won't break any website.