[System Health] Extend dump time to 5 seconds

[System Health] Extend dump time to 5 seconds

Experiments have shown this significantly reduces noise
levels un gpu and cc memory infra metrics.

BUG=chromium:734853
Review-Url: https://codereview.chromium.org/2946013004
Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/b4eb70c319cb0f38d1a7764e7d9fb56dc96f8bcf

[perezju, 2017-06-26 10:40:57]

Description was changed from

==========
[Experiment] Extend dump time to 5 seconds

BUG=chromium:734853
==========

to

==========
[System Health] Extend dump time to 5 seconds

Experiments have shown this significantly reduces noise
levels un gpu and cc memory infra metrics.

BUG=chromium:734853
==========

[perezju, 2017-06-26 10:42:23]

perezju@chromium.org changed reviewers:
+ ericrk@chromium.org, nednguyen@google.com, primiano@chromium.org

[Primiano Tucci (use gerrit), 2017-06-26 12:06:01]

lgtm

[nednguyen, 2017-06-26 13:20:00]

On 2017/06/26 12:06:01, Primiano Tucci wrote:
> lgtm

I think we may need to extend the time out in
https://cs.chromium.org/chromium/src/tools/perf/core/perf_data_generator.py?r...
first before landing this

lgtm

[perezju, 2017-06-26 13:52:54]

On 2017/06/26 at 13:20:00, nednguyen wrote:
> On 2017/06/26 12:06:01, Primiano Tucci wrote:
> > lgtm
> 
> I think we may need to extend the time out in
https://cs.chromium.org/chromium/src/tools/perf/core/perf_data_generator.py?r...
first before landing this
> 
> lgtm

I was trying to get all bots on:

https://chromeperf.appspot.com/report?sid=73544cadd495214531bf4cb0a0f15fb800c...

But got bored after a while. Anyway, looks like the benchmarks takes most (~150
mins) on Android One's.
This CL should add extra 13 minutes to it, close but still under the current 3
hours timeout.

Should I leave the timeout as is? Or bump it up by, say, 15 minutes?

[nednguyen, 2017-06-26 13:58:35]

On 2017/06/26 13:52:54, perezju wrote:
> On 2017/06/26 at 13:20:00, nednguyen wrote:
> > On 2017/06/26 12:06:01, Primiano Tucci wrote:
> > > lgtm
> > 
> > I think we may need to extend the time out in
>
https://cs.chromium.org/chromium/src/tools/perf/core/perf_data_generator.py?r...
> first before landing this
> > 
> > lgtm
> 
> I was trying to get all bots on:
> 
>
https://chromeperf.appspot.com/report?sid=73544cadd495214531bf4cb0a0f15fb800c...
> 
> But got bored after a while. Anyway, looks like the benchmarks takes most
(~150
> mins) on Android One's.
> This CL should add extra 13 minutes to it, close but still under the current 3
> hours timeout.
> 
> Should I leave the timeout as is? Or bump it up by, say, 15 minutes?

Ok. We can watch out the waterfall closely and then bump it if any bot timed
out.

[perezju, 2017-06-26 14:00:41]

The CQ bit was checked by perezju@chromium.org

[commit-bot: I haz the power, 2017-06-26 14:00:51]

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-26 14:25:41]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1498485641261460,
"parent_rev": "d4f2d777c7aa4d9454a74afe92ff17e13da62380", "commit_rev":
"b4eb70c319cb0f38d1a7764e7d9fb56dc96f8bcf"}

[commit-bot: I haz the power, 2017-06-26 14:25:47]

Description was changed from

==========
[System Health] Extend dump time to 5 seconds

Experiments have shown this significantly reduces noise
levels un gpu and cc memory infra metrics.

BUG=chromium:734853
==========

to

==========
[System Health] Extend dump time to 5 seconds

Experiments have shown this significantly reduces noise
levels un gpu and cc memory infra metrics.

BUG=chromium:734853

Review-Url: https://codereview.chromium.org/2946013004
Committed:
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...
==========

[commit-bot: I haz the power, 2017-06-26 14:25:48]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...

[perezju, 2017-07-08 08:53:33]

A revert of this CL (patchset #2 id:20001) has been created in
https://codereview.chromium.org/2973253003/ by perezju@chromium.org.

The reason for reverting is: Did not provide intended effect on the waterfall.

Note to perf sheriffs: This is expected to cause several metric values to
shift..