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

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


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

android-webview-nexus5X
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia

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

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

Hi leszeks@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 : Leszek Swirski
  Commit : a2fcdc7cc8b286941ca054bf62c8a51166e39379
  Date   : Wed Jul 05 12:04:50 2017
  Subject: [runtime] Move profiler ticks from SFI to feedback vector

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : Optimize:duration_avg/browse_media/browse_media_youtube
  Change       : 129.57% | 6.98316666667 -> 16.031

Revision                           Result                  N
chromium@484264                    6.98317 +- 2.65162      6      good
chromium@484273                    7.09217 +- 1.87081      6      good
chromium@484278                    7.60033 +- 3.54137      6      good
chromium@484279                    7.047 +- 2.76136        6      good
chromium@484279,v8@b2644df70f      8.91817 +- 4.99383      6      good
chromium@484279,v8@6886f2ceed      8.156 +- 4.70516        6      good
chromium@484279,v8@a2fcdc7cc8      15.5807 +- 3.92557      6      bad       <--
chromium@484280                    14.882 +- 3.53971       6      bad
chromium@484282                    16.1507 +- 2.03726      6      bad
chromium@484300                    14.6833 +- 6.4781       6      bad
chromium@484335                    16.031 +- 9.51572       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=browse.media.youtube v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection

 Issue 740923  has been merged into this issue.

Reverted in https://chromium-review.googlesource.com/c/574227/