All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=724468

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2qu4ugoM


Bot(s) for this bug's original alert(s):

android-nexus6

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979166504166279504

This happens right around the move to swarming. I suspect that we may be shuffling the benchmark to a different bot, hence the cycle time increase :-?

What is strange though, is the cycle time of ref build doesn't change. So this could totally be  due to Chrome/Telemetry change. Let wait for the bisect result.

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : benchmark_duration/benchmark_duration

Revision             Result                  N
chromium@472224      5.82965 +- 1.33187      21      good
chromium@472383      5.6903 +- 0.93447       21      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979166504166279504

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5240352870498304


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979148470967567824

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : benchmark_duration/benchmark_duration

Revision             Result                  N
chromium@472224      5.92818 +- 2.68778      21      good
chromium@472383      6.44946 +- 5.15011      21      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979148470967567824

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5240352870498304


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!