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

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


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

chromium-rel-win7-dual

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

=== 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    : speedometer2
  Metric       : Total/Speedometer2
  Change       : 4.44% | 6451.77083333 -> 6738.0845

Revision             Result                  N
chromium@505470      6451.77 +- 35.2306      6      good
chromium@505487      6451.69 +- 27.8013      6      good
chromium@505491      6476.69 +- 45.634       6      good
chromium@505493      6448.93 +- 54.8393      6      good
chromium@505494      6748.99 +- 79.7069      6      bad       <--
chromium@505495      6742.39 +- 93.847       6      bad
chromium@505503      6738.08 +- 26.648       6      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=Speedometer2 speedometer2

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

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


For feedback, file a bug with component Speed>Bisection