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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=168f134240d6f86944728d76f6094aa77717e0c2c28d5bec84df88f6b79d1a08


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

chromium-rel-win7-dual

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

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

Suspected Commit
  Author : Justin Schuh
  Commit : 3725ec39917fea4cc350f0abb8dde4552e955054
  Date   : Sun Oct 01 03:44:27 2017
  Subject: Make ClampedNumeric and CheckedNumeric constexpr

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : blink_perf.layout
  Metric       : floats_20_100/floats_20_100
  Change       : 80.71% | 377.948 -> 682.987666667

Revision             Result                  N
chromium@505470      377.948 +- 1.55025      6      good
chromium@505487      378.045 +- 2.81862      6      good
chromium@505491      378.328 +- 1.77438      6      good
chromium@505493      378.808 +- 3.38558      6      good
chromium@505494      683.227 +- 1.03664      6      bad       <--
chromium@505495      683.769 +- 1.44257      6      bad
chromium@505503      682.988 +- 1.54802      6      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

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

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8966741957907801088


For feedback, file a bug with component Speed>Bisection