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

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


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

chromium-rel-win10

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

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

Suspected Commit
  Author : keishi
  Commit : 51ed0d54153a164e68155447fcd1cfcb393f1870
  Date   : Thu Jan 12 10:04:46 2017
  Subject: Add renderer memory metrics

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : blink_perf.layout
  Metric       : Shapes_MultipleShapes/Shapes_MultipleShapes
  Change       : 24.28% | 15.978 -> 19.8581666667

Revision             Result                   N
chromium@443167      15.978 +- 0.856392       6      good
chromium@443182      15.9033 +- 0.207662      6      good
chromium@443190      16.1462 +- 0.589975      6      good
chromium@443194      16.0108 +- 0.389282      6      good
chromium@443195      20.1368 +- 0.919103      6      bad       <--
chromium@443196      20.1537 +- 0.304147      6      bad
chromium@443197      19.8582 +- 0.651586      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.layout

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

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


| 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 Tests>AutoBisect.  Thank you!