Remove MemoryCondition::WARNING

Remove MemoryCondition::WARNING

It's not clear that having WARNING condition helps us to build a
reasonable policy to handle memory pressure. Just use a binary
(NORMAL and CRITICAL) until we really need it.

This CL also simplifies the heuristic to estimate memory pressure
to reduce complexity.

BUG=696844
Review-Url: https://codereview.chromium.org/2943603002
Cr-Commit-Position: refs/heads/master@{#480336}
Committed: https://chromium.googlesource.com/chromium/src/+/1960d03cec25ebdf6d8d14a06e2eeebf19debcc2

[bashi, 2017-06-16 02:17:14]

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

[commit-bot: I haz the power, 2017-06-16 02:17:33]

Dry run: CQ is trying da patch.

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

[bashi, 2017-06-16 02:20:14]

Description was changed from

==========
Remove MemoryCondition::WARNING

It's not clear that having WARNING condition helps us to build a
reasonable policy to handle memory pressure. Just use a binary
(NORMAL and CRITICAL) until we really need it.

BUG=696844
==========

to

==========
Remove MemoryCondition::WARNING

It's not clear that having WARNING condition helps us to build a
reasonable policy to handle memory pressure. Just use a binary
(NORMAL and CRITICAL) until we really need it.

This CL also simplifies the heuristic to estimate memory pressure
to reduce complexity.

BUG=696844
==========

[bashi, 2017-06-16 02:21:56]

bashi@chromium.org changed reviewers:
+ chrisha@chromium.org, haraken@chromium.org

[bashi, 2017-06-16 02:21:56]

PTAL

[haraken, 2017-06-16 02:23:10]

LGTM

[commit-bot: I haz the power, 2017-06-16 02:48:56]

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

[commit-bot: I haz the power, 2017-06-16 02:48:57]

Dry run: Try jobs failed on following builders:
  cast_shell_android on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...)

[bashi, 2017-06-16 03:07:41]

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

[commit-bot: I haz the power, 2017-06-16 03:07:50]

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, 2017-06-16 04:30:28]

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

[commit-bot: I haz the power, 2017-06-16 04:30:30]

Dry run: This issue passed the CQ dry run.

[chrisha, 2017-06-16 17:26:27]

lgtm

[bashi, 2017-06-19 01:54:26]

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

[commit-bot: I haz the power, 2017-06-19 01:54:38]

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, 2017-06-19 03:14:40]

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

[commit-bot: I haz the power, 2017-06-19 03:14:41]

Dry run: This issue passed the CQ dry run.

[bashi, 2017-06-19 03:21:54]

The CQ bit was checked by bashi@chromium.org

[bashi, 2017-06-19 03:21:54]

The patchset sent to the CQ was uploaded after l-g-t-m from
haraken@chromium.org, chrisha@chromium.org
Link to the patchset: https://codereview.chromium.org/2943603002/#ps40001
(title: "rebase")

[commit-bot: I haz the power, 2017-06-19 03:22:02]

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, 2017-06-19 03:26:01]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1497842514247710,
"parent_rev": "eebe90a681e08afaf51f3865e7f60e8d95626c79", "commit_rev":
"1960d03cec25ebdf6d8d14a06e2eeebf19debcc2"}

[commit-bot: I haz the power, 2017-06-19 03:26:13]

Description was changed from

==========
Remove MemoryCondition::WARNING

It's not clear that having WARNING condition helps us to build a
reasonable policy to handle memory pressure. Just use a binary
(NORMAL and CRITICAL) until we really need it.

This CL also simplifies the heuristic to estimate memory pressure
to reduce complexity.

BUG=696844
==========

to

==========
Remove MemoryCondition::WARNING

It's not clear that having WARNING condition helps us to build a
reasonable policy to handle memory pressure. Just use a binary
(NORMAL and CRITICAL) until we really need it.

This CL also simplifies the heuristic to estimate memory pressure
to reduce complexity.

BUG=696844

Review-Url: https://codereview.chromium.org/2943603002
Cr-Commit-Position: refs/heads/master@{#480336}
Committed:
https://chromium.googlesource.com/chromium/src/+/1960d03cec25ebdf6d8d14a06e2e...
==========

[commit-bot: I haz the power, 2017-06-19 03:26:13]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/1960d03cec25ebdf6d8d14a06e2e...