[scheduler] Throttle background frames with 1% CPU limit

[scheduler] Throttle background frames with 1% CPU limit

BUG=639852, 653865
Committed: https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Committed: https://crrev.com/ac51fd04eefe80d22ecd5d0898fafad906f70f22
Committed: https://crrev.com/1fca2bed4bacd6fb1dc7ffacd4c2d92d59ceae8f
Cr-Original-Original-Commit-Position: refs/heads/master@{#423170}
Cr-Original-Commit-Position: refs/heads/master@{#423604}
Cr-Commit-Position: refs/heads/master@{#424850}

[altimin, 2016-09-27 15:56:19]

altimin@chromium.org changed reviewers:
+ alexclarke@chromium.org, skyostil@chromium.org

[altimin, 2016-09-27 15:56:20]

PTAL

[alex clarke (OOO till 29th), 2016-09-27 16:32:10]

https://codereview.chromium.org/2345483002/diff/40001/content/public/common/c...
File content/public/common/content_features.cc (right):

https://codereview.chromium.org/2345483002/diff/40001/content/public/common/c...
content/public/common/content_features.cc:39: // for the background tab. Bug:
crbug.com/639852.
Maybe: See http://crbug.com/639852

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
File
third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.cc
(right):

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.cc:21:
const double kBackgroundCPUBudget = .01;
Maybe  s/kBackgroundCPUBudget/kBackgroundCPUBudgetFraction

[Sami, 2016-09-27 17:11:56]

Looks great.

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/platform/RuntimeEnabledFeatures.in (right):

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/RuntimeEnabledFeatures.in:85:
ExpensiveBackgroundTimerThrottling status=experimental
There's already a TimerThrottlingForBackgroundTabs feature. I wonder if we could
name this so that it's clear how they're related? Maybe
BudgetBasedTimerThrottlingForBackgroundTabs?

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
File
third_party/WebKit/Source/platform/scheduler/renderer/web_frame_scheduler_impl.cc
(right):

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/scheduler/renderer/web_frame_scheduler_impl.cc:59:
TaskQueueThrottler::TimeBudgetPool* time_budget_pool =
Why do we need to do this here and also the destructor?

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
File
third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.h
(right):

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.h:62:
friend class WebFrameSchedulerImpl;
Instead of this could we just adjust the public API so that the frame scheduler
can do its thing?

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.h:78:
TaskQueueThrottler::TimeBudgetPool* background_time_budget_pool_;
Not owned?

[alex clarke (OOO till 29th), 2016-09-27 17:16:23]

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
File
third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.h
(right):

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.h:62:
friend class WebFrameSchedulerImpl;
On 2016/09/27 17:11:56, Sami wrote:
> Instead of this could we just adjust the public API so that the frame
scheduler
> can do its thing?

+1

[altimin, 2016-09-27 17:38:23]

PTAL

https://codereview.chromium.org/2345483002/diff/40001/content/public/common/c...
File content/public/common/content_features.cc (right):

https://codereview.chromium.org/2345483002/diff/40001/content/public/common/c...
content/public/common/content_features.cc:39: // for the background tab. Bug:
crbug.com/639852.
On 2016/09/27 16:32:10, alex clarke wrote:
> Maybe: See http://crbug.com/639852

https :) Done.

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/platform/RuntimeEnabledFeatures.in (right):

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/RuntimeEnabledFeatures.in:85:
ExpensiveBackgroundTimerThrottling status=experimental
On 2016/09/27 17:11:56, Sami wrote:
> There's already a TimerThrottlingForBackgroundTabs feature. I wonder if we
could
> name this so that it's clear how they're related? Maybe
> BudgetBasedTimerThrottlingForBackgroundTabs?

I believe that word "Expensive" explains the difference (and gives more
information than "BudgetBased" to a newcomer).

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
File
third_party/WebKit/Source/platform/scheduler/renderer/web_frame_scheduler_impl.cc
(right):

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/scheduler/renderer/web_frame_scheduler_impl.cc:59:
TaskQueueThrottler::TimeBudgetPool* time_budget_pool =
On 2016/09/27 17:11:56, Sami wrote:
> Why do we need to do this here and also the destructor?

Because:
a) We need to do it here because we're losing handle to
parent_web_view_scheduler_ here.
b) We need to do it in destructor because DetachFromWebViewScheduler might not
be called before destructor.

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
File
third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.cc
(right):

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.cc:21:
const double kBackgroundCPUBudget = .01;
On 2016/09/27 16:32:10, alex clarke wrote:
> Maybe  s/kBackgroundCPUBudget/kBackgroundCPUBudgetFraction

Done.

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
File
third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.h
(right):

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.h:62:
friend class WebFrameSchedulerImpl;
On 2016/09/27 17:16:23, alex clarke wrote:
> On 2016/09/27 17:11:56, Sami wrote:
> > Instead of this could we just adjust the public API so that the frame
> scheduler
> > can do its thing?
> 
> +1

Done.

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.h:78:
TaskQueueThrottler::TimeBudgetPool* background_time_budget_pool_;
On 2016/09/27 17:11:56, Sami wrote:
> Not owned?

Done.

[Sami, 2016-09-29 09:32:29]

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
File
third_party/WebKit/Source/platform/scheduler/renderer/web_frame_scheduler_impl.cc
(right):

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/scheduler/renderer/web_frame_scheduler_impl.cc:59:
TaskQueueThrottler::TimeBudgetPool* time_budget_pool =
On 2016/09/27 17:38:23, altimin wrote:
> On 2016/09/27 17:11:56, Sami wrote:
> > Why do we need to do this here and also the destructor?
> 
> Because:
> a) We need to do it here because we're losing handle to
> parent_web_view_scheduler_ here.
> b) We need to do it in destructor because DetachFromWebViewScheduler might not
> be called before destructor.

I see. Could we instead call DetachFromWebViewScheduler() conditionally in the
destructor?

[altimin, 2016-09-29 12:32:38]

PTAL

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
File
third_party/WebKit/Source/platform/scheduler/renderer/web_frame_scheduler_impl.cc
(right):

https://codereview.chromium.org/2345483002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/scheduler/renderer/web_frame_scheduler_impl.cc:59:
TaskQueueThrottler::TimeBudgetPool* time_budget_pool =
On 2016/09/29 09:32:29, Sami wrote:
> On 2016/09/27 17:38:23, altimin wrote:
> > On 2016/09/27 17:11:56, Sami wrote:
> > > Why do we need to do this here and also the destructor?
> > 
> > Because:
> > a) We need to do it here because we're losing handle to
> > parent_web_view_scheduler_ here.
> > b) We need to do it in destructor because DetachFromWebViewScheduler might
not
> > be called before destructor.
> 
> I see. Could we instead call DetachFromWebViewScheduler() conditionally in the
> destructor?

It will be ugly. Lets just call RemoveTimerQueueFromBackgroundTimeBudgetPool
from both places.

[altimin, 2016-09-29 12:32:39]

PTAL

[Sami, 2016-09-29 13:04:19]

Thanks, lgtm.

[altimin, 2016-09-29 13:09:07]

altimin@chromium.org changed reviewers:
+ jochen@chromium.org

[altimin, 2016-09-29 13:09:08]

+ jochen@ for all flag and features related changes

[altimin, 2016-09-29 17:24:38]

The CQ bit was checked by altimin@chromium.org

[commit-bot: I haz the power, 2016-09-29 17:25:17]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-29 17:35:59]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-29 17:36:02]

Try jobs failed on following builders:
  chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[jochen (gone - plz use gerrit), 2016-09-30 10:58:04]

https://codereview.chromium.org/2345483002/diff/80001/chrome/app/generated_re...
File chrome/app/generated_resources.grd (right):

https://codereview.chromium.org/2345483002/diff/80001/chrome/app/generated_re...
chrome/app/generated_resources.grd:15525: +    <message
name="IDS_FLAGS_EXPENSIVE_BACKGROUND_TIMER_THROTTLING_NAME">
please add a desc="" describing what this message is used for (and below)

[jochen (gone - plz use gerrit), 2016-09-30 10:58:25]

btw, why do you need a content feature (as opposed to just a command line flag)?

[Sami, 2016-09-30 11:04:47]

On 2016/09/30 10:58:25, jochen (slow) wrote:
> btw, why do you need a content feature (as opposed to just a command line
flag)?

Finch is a bit more convenient with content features as opposed to command line
flags.

[altimin, 2016-09-30 11:37:17]

The CQ bit was checked by altimin@chromium.org

[altimin, 2016-09-30 11:37:18]

The patchset sent to the CQ was uploaded after l-g-t-m from
skyostil@chromium.org
Link to the patchset: https://codereview.chromium.org/2345483002/#ps100001
(title: "Add comments to resources.grd for jochen@")

[commit-bot: I haz the power, 2016-09-30 11:37:28]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[altimin, 2016-09-30 11:37:36]

PTAL

https://codereview.chromium.org/2345483002/diff/80001/chrome/app/generated_re...
File chrome/app/generated_resources.grd (right):

https://codereview.chromium.org/2345483002/diff/80001/chrome/app/generated_re...
chrome/app/generated_resources.grd:15525: +    <message
name="IDS_FLAGS_EXPENSIVE_BACKGROUND_TIMER_THROTTLING_NAME">
On 2016/09/30 10:58:03, jochen (slow) wrote:
> please add a desc="" describing what this message is used for (and below)

Done.

[altimin, 2016-09-30 11:38:42]

The CQ bit was unchecked by altimin@chromium.org

[altimin, 2016-09-30 11:39:03]

The CQ bit was checked by altimin@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-09-30 11:39:17]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-30 12:26:02]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-30 12:26:03]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[jochen (gone - plz use gerrit), 2016-10-04 14:40:11]

lgtm

[altimin, 2016-10-04 15:30:00]

The CQ bit was checked by altimin@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-04 15:30:14]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[altimin, 2016-10-04 15:31:07]

altimin@chromium.org changed reviewers:
+ mpearson@chromium.org

[altimin, 2016-10-04 15:31:08]

+mpearson@ for histograms.xml change

[commit-bot: I haz the power, 2016-10-04 15:32:44]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-04 15:32:45]

Dry run: Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
  ios-simulator on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)

[altimin, 2016-10-04 15:50:02]

The CQ bit was checked by altimin@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-04 15:50:20]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Mark P, 2016-10-04 15:56:16]

histograms.xml lgtm

[altimin, 2016-10-04 15:57:18]

The CQ bit was unchecked by altimin@chromium.org

[altimin, 2016-10-04 15:57:19]

The CQ bit was checked by altimin@chromium.org

[altimin, 2016-10-04 15:57:19]

The patchset sent to the CQ was uploaded after l-g-t-m from jochen@chromium.org,
skyostil@chromium.org
Link to the patchset: https://codereview.chromium.org/2345483002/#ps140001
(title: "Updated histograms.xml to fix CustomLoginFlags failure")

[commit-bot: I haz the power, 2016-10-04 15:57:42]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-04 17:19:21]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-04 17:19:22]

Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[altimin, 2016-10-04 17:43:36]

The CQ bit was checked by altimin@chromium.org

[commit-bot: I haz the power, 2016-10-04 17:44:14]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-04 18:32:56]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-04 18:32:57]

Try jobs failed on following builders:
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[altimin, 2016-10-05 11:55:02]

The CQ bit was checked by altimin@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-05 11:55:10]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-05 11:57:47]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-05 11:57:49]

Dry run: Try jobs failed on following builders:
  mac_chromium_compile_dbg_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)

[alex clarke (OOO till 29th), 2016-10-05 12:01:54]

lgtm

https://codereview.chromium.org/2345483002/diff/160001/third_party/WebKit/Sou...
File
third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.cc
(right):

https://codereview.chromium.org/2345483002/diff/160001/third_party/WebKit/Sou...
third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.cc:48:
background_time_budget_pool_->DisableThrottling(&lazy_now);
Please add a comment explaining why this is needed.

[altimin, 2016-10-05 12:10:14]

The CQ bit was checked by altimin@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-05 12:10:20]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-05 13:52:38]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-05 13:52:39]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[altimin, 2016-10-05 13:54:15]

The CQ bit was checked by altimin@chromium.org

[altimin, 2016-10-05 13:54:16]

The patchset sent to the CQ was uploaded after l-g-t-m from jochen@chromium.org,
mpearson@chromium.org, skyostil@chromium.org, alexclarke@chromium.org
Link to the patchset: https://codereview.chromium.org/2345483002/#ps180001
(title: "Rebased & added test & added comment")

[commit-bot: I haz the power, 2016-10-05 13:54:34]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-05 15:53:28]

Committed patchset #10 (id:180001)

[commit-bot: I haz the power, 2016-10-05 15:55:35]

Description was changed from

==========
[scheduler] Throttle background frames with 1% CPU limit

BUG=639852
==========

to

==========
[scheduler] Throttle background frames with 1% CPU limit

BUG=639852

Committed: https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Cr-Commit-Position: refs/heads/master@{#423170}
==========

[commit-bot: I haz the power, 2016-10-05 15:55:37]

Patchset 10 (id:??) landed as
https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Cr-Commit-Position: refs/heads/master@{#423170}

[altimin, 2016-10-06 14:16:41]

Description was changed from

==========
[scheduler] Throttle background frames with 1% CPU limit

BUG=639852

Committed: https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Cr-Commit-Position: refs/heads/master@{#423170}
==========

to

==========
[scheduler] Throttle background frames with 1% CPU limit

BUG=639852

Committed: https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Cr-Commit-Position: refs/heads/master@{#423170}
==========

[altimin, 2016-10-06 14:16:52]

The CQ bit was checked by altimin@chromium.org

[altimin, 2016-10-06 14:16:53]

The patchset sent to the CQ was uploaded after l-g-t-m from jochen@chromium.org,
mpearson@chromium.org, skyostil@chromium.org, alexclarke@chromium.org
Link to the patchset: https://codereview.chromium.org/2345483002/#ps200001
(title: "Fixed SetQueueEnabled bug")

[commit-bot: I haz the power, 2016-10-06 14:17:16]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-06 18:44:58]

Description was changed from

==========
[scheduler] Throttle background frames with 1% CPU limit

BUG=639852

Committed: https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Cr-Commit-Position: refs/heads/master@{#423170}
==========

to

==========
[scheduler] Throttle background frames with 1% CPU limit

BUG=639852

Committed: https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Cr-Commit-Position: refs/heads/master@{#423170}
==========

[commit-bot: I haz the power, 2016-10-06 18:45:00]

Committed patchset #11 (id:200001)

[commit-bot: I haz the power, 2016-10-06 18:47:11]

Description was changed from

==========
[scheduler] Throttle background frames with 1% CPU limit

BUG=639852

Committed: https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Cr-Commit-Position: refs/heads/master@{#423170}
==========

to

==========
[scheduler] Throttle background frames with 1% CPU limit

BUG=639852

Committed: https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Committed: https://crrev.com/ac51fd04eefe80d22ecd5d0898fafad906f70f22
Cr-Original-Commit-Position: refs/heads/master@{#423170}
Cr-Commit-Position: refs/heads/master@{#423604}
==========

[commit-bot: I haz the power, 2016-10-06 18:47:12]

Patchset 11 (id:??) landed as
https://crrev.com/ac51fd04eefe80d22ecd5d0898fafad906f70f22
Cr-Commit-Position: refs/heads/master@{#423604}

[altimin, 2016-10-12 18:59:28]

Description was changed from

==========
[scheduler] Throttle background frames with 1% CPU limit

BUG=639852

Committed: https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Committed: https://crrev.com/ac51fd04eefe80d22ecd5d0898fafad906f70f22
Cr-Original-Commit-Position: refs/heads/master@{#423170}
Cr-Commit-Position: refs/heads/master@{#423604}
==========

to

==========
[scheduler] Throttle background frames with 1% CPU limit

BUG=639852, 653865

Committed: https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Committed: https://crrev.com/ac51fd04eefe80d22ecd5d0898fafad906f70f22
Cr-Original-Commit-Position: refs/heads/master@{#423170}
Cr-Commit-Position: refs/heads/master@{#423604}
==========

[altimin, 2016-10-12 18:59:39]

The CQ bit was checked by altimin@chromium.org

[altimin, 2016-10-12 18:59:40]

The patchset sent to the CQ was uploaded after l-g-t-m from jochen@chromium.org,
mpearson@chromium.org, skyostil@chromium.org, alexclarke@chromium.org
Link to the patchset: https://codereview.chromium.org/2345483002/#ps220001
(title: "Rebased")

[commit-bot: I haz the power, 2016-10-12 19:00:24]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-12 21:07:11]

Description was changed from

==========
[scheduler] Throttle background frames with 1% CPU limit

BUG=639852, 653865

Committed: https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Committed: https://crrev.com/ac51fd04eefe80d22ecd5d0898fafad906f70f22
Cr-Original-Commit-Position: refs/heads/master@{#423170}
Cr-Commit-Position: refs/heads/master@{#423604}
==========

to

==========
[scheduler] Throttle background frames with 1% CPU limit

BUG=639852, 653865

Committed: https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Committed: https://crrev.com/ac51fd04eefe80d22ecd5d0898fafad906f70f22
Cr-Original-Commit-Position: refs/heads/master@{#423170}
Cr-Commit-Position: refs/heads/master@{#423604}
==========

[commit-bot: I haz the power, 2016-10-12 21:07:15]

Committed patchset #12 (id:220001)

[commit-bot: I haz the power, 2016-10-12 21:10:53]

Description was changed from

==========
[scheduler] Throttle background frames with 1% CPU limit

BUG=639852, 653865

Committed: https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Committed: https://crrev.com/ac51fd04eefe80d22ecd5d0898fafad906f70f22
Cr-Original-Commit-Position: refs/heads/master@{#423170}
Cr-Commit-Position: refs/heads/master@{#423604}
==========

to

==========
[scheduler] Throttle background frames with 1% CPU limit

BUG=639852, 653865

Committed: https://crrev.com/e25269603f52b2f26ab6db689f730af15a2607da
Committed: https://crrev.com/ac51fd04eefe80d22ecd5d0898fafad906f70f22
Committed: https://crrev.com/1fca2bed4bacd6fb1dc7ffacd4c2d92d59ceae8f
Cr-Original-Original-Commit-Position: refs/heads/master@{#423170}
Cr-Original-Commit-Position: refs/heads/master@{#423604}
Cr-Commit-Position: refs/heads/master@{#424850}
==========

[commit-bot: I haz the power, 2016-10-12 21:10:55]

Patchset 12 (id:??) landed as
https://crrev.com/1fca2bed4bacd6fb1dc7ffacd4c2d92d59ceae8f
Cr-Commit-Position: refs/heads/master@{#424850}