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

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


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

android-webview-nexus5X
chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac12-mini-8gb
chromium-rel-win7-x64-dual
linux-release

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

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

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

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

Hi thomasanderson@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 : Tom Anderson
  Commit : 14b00f61f942f7667aaf15fdd184844c7a43d979
  Date   : Thu Sep 28 21:10:35 2017
  Subject: Linux native notifications: Make notifications timeout after 25s

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : speedometer2
  Metric       : EmberJS-TodoMVC/Speedometer2
  Change       : 2.88% | 1871.18741667 -> 1924.99358333

Revision             Result                  N
chromium@505126      1871.19 +- 54.6714      6      good
chromium@505150      1818.86 +- 34.3319      6      good
chromium@505153      1783.63 +- 26.5109      6      good
chromium@505155      1800.09 +- 27.9917      6      good
chromium@505156      1884.73 +- 39.4963      6      bad       <--
chromium@505162      1914.68 +- 50.0787      6      bad
chromium@505173      1932.2 +- 41.7237       6      bad
chromium@505220      1924.99 +- 31.2228      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/8966510970417597872


For feedback, file a bug with component Speed>Bisection

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

Hi verwaest@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 : Toon Verwaest
  Commit : b8b25e1c27b6634b764245671b5fcaacb19278bf
  Date   : Thu Sep 28 11:24:12 2017
  Subject: [ic] Remove extra-ic-state and Map::code_cache

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : speedometer2
  Metric       : EmberJS-TodoMVC/Speedometer2
  Change       : 3.07% | 1872.51575 -> 1929.91875

Revision                           Result                  N
chromium@505126                    1872.52 +- 20.6137      6      good
chromium@505150                    1808.42 +- 21.0833      6      good
chromium@505156                    1862.49 +- 20.8533      6      good
chromium@505156,v8@329f694678      1814.27 +- 28.7968      6      good
chromium@505156,v8@690d52afa8      1815.05 +- 30.5754      6      good
chromium@505156,v8@b8b25e1c27      1903.67 +- 27.4009      6      bad       <--
chromium@505156,v8@70abcb06ae      1945.88 +- 23.3878      6      bad
chromium@505157                    1943.56 +- 26.5787      6      bad
chromium@505158                    1921.67 +- 29.7088      6      bad
chromium@505159                    1945.25 +- 33.5976      6      bad
chromium@505162                    1917.16 +- 24.0382      6      bad
chromium@505173                    1942.54 +- 29.0637      6      bad
chromium@505220                    1929.92 +- 31.5976      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/8966510870772871920


For feedback, file a bug with component Speed>Bisection

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : speedometer2
  Metric       : Total/Speedometer2
  Change       : 0.50% | 32795.3174074 -> 32959.7116667

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/020d22695214c706ed96c6d05356ee83f4cc1acd..667369731fdcdcb65b6a38b8178d8abe2cd20551


Revision             Result                  N
chromium@505115      32795.3 +- 322.866      9        good
chromium@505146      32718.0 +- 531.151      14       good
chromium@505147      ---                     ---      build failure
chromium@505148      ---                     ---      build failure
chromium@505149      32842.5 +- 535.294      14       bad
chromium@505150      32840.6 +- 479.15       14       bad
chromium@505154      32884.0 +- 520.064      14       bad
chromium@505161      32987.4 +- 309.182      9        bad
chromium@505176      32959.7 +- 449.692      9        bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --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/8966511532935363344


For feedback, file a bug with component Speed>Bisection

 Issue 772704  has been merged into this issue.

Code-based handlers are going away soon, so I don't think it's worth jumping through hoops here now for a slight speedometer regression.