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

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


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

chromium-rel-win7-gpu-intel

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

=== Auto-CCing suspected CL author cbruni@chromium.org ===

Hi cbruni@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Camillo Bruni
  Commit : 808dc8cff3f6530a627ade106cbd814d16a10a18
  Date   : Wed Oct 04 13:06:49 2017
  Subject: Support fast-path Function.prototype.bind for bound function

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : speedometer2
  Metric       : React-Redux-TodoMVC/Speedometer2
  Change       : 5.42% | 439.943416667 -> 463.797666667

Revision                           Result                  N
chromium@506671                    439.943 +- 12.6759      6      good
chromium@506693                    450.5 +- 9.12198        6      good
chromium@506696                    442.16 +- 10.3797       6      good
chromium@506698                    444.195 +- 10.2294      6      good
chromium@506698,v8@ec489f39c1      442.597 +- 6.36517      6      good
chromium@506698,v8@808dc8cff3      470.787 +- 10.4125      6      bad       <--
chromium@506698,v8@947101c873      468.19 +- 10.6941       6      bad
chromium@506698,v8@cbd03a8379      463.027 +- 6.15322      6      bad
chromium@506698,v8@f3fb1b7798      470.109 +- 13.3231      6      bad
chromium@506699                    461.958 +- 8.97438      6      bad
chromium@506704                    468.819 +- 9.56885      6      bad
chromium@506714                    463.798 +- 13.1709      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 --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/8966363991713136528


For feedback, file a bug with component Speed>Bisection

This seems fairly inconsistent across bots:
https://chromeperf.appspot.com/report?sid=16194f663872c5aa5b8b63fab27836e87eb65796816b2f3483b07dbd222d2239&start_rev=503175&end_rev=507307

Will investigate.

Given that mostly only the win=7 GPU were affect I will mark this as WontFix.