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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7IO47wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7IO2kAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnIbhtwoM


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

chromium-rel-win8-dual

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : sugoi
  Commit : 7ae2ba1892a8b4dee8d7c231ac0e0fbe66588912
  Date   : Sat Mar 25 13:59:47 2017
  Subject: Solving some telemetry tests' slowness

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstContentfulPaint_avg/load_tools/load_tools_maps
  Change       : 51.18% | 1182.92621429 -> 1788.32655556

Revision             Result                  N
chromium@459649      1182.93 +- 1501.74      14      good
chromium@459650      1075.48 +- 174.456      6       good
chromium@459651      2014.39 +- 3465.14      6       bad       <--
chromium@459653      1897.89 +- 2779.62      6       bad
chromium@459656      1806.17 +- 2660.72      6       bad
chromium@459662      1788.33 +- 2641.36      9       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.maps system_health.common_desktop

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

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


| 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!