diff options
author | perezju <perezju@chromium.org> | 2016-02-26 12:56:36 -0800 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2016-02-26 20:59:20 +0000 |
commit | e8624b7e4da924dc95798d4d8cedd34b27bfb4b5 (patch) | |
tree | 3761362a54b4df5e9834ead359d374462200f6ed /net/base | |
parent | fe11616891b5f57ea977c24efdf7946ed2cbf5f7 (diff) | |
download | chromium_src-e8624b7e4da924dc95798d4d8cedd34b27bfb4b5.zip chromium_src-e8624b7e4da924dc95798d4d8cedd34b27bfb4b5.tar.gz chromium_src-e8624b7e4da924dc95798d4d8cedd34b27bfb4b5.tar.bz2 |
Revert of memory_health_story: Extend the initial wait time by 8x. (patchset #1 id:1 of https://codereview.chromium.org/1713943002/ )
Reason for revert:
We've got some data for a couple of days. So finishing the experiment now.
Original issue's description:
> memory_health_story: Extend the initial wait time by 8x.
>
> The amount of wait before starting to run a GC and taking the snapshot
> of memory was originally set to 3 seconds, but this seemed too short for
> low-memory devices to reach a stable state. Due to this, Oilpan objects
> were still actively allocated even after the GC was run, causing the
> memory usage of this test looking worse due to Oilpan.
>
> This patch is a temporary band-aid to see if extending the wait time
> improves the situation on the bots. On my local environment it did.
>
> BUG=581422
> R=nednguyen@google.com
>
> Committed: https://crrev.com/b1617118e38e711e7c282e50247c6f9736470aa6
> Cr-Commit-Position: refs/heads/master@{#376725}
TBR=nednguyen@google.com,picksi@chromium.org,primiano@chromium.org,haraken@chromium.org,yutak@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=581422
Review URL: https://codereview.chromium.org/1744593002
Cr-Commit-Position: refs/heads/master@{#377974}
Diffstat (limited to 'net/base')
0 files changed, 0 insertions, 0 deletions