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

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


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

android-nexus5
android-nexus5X
android-nexus6
android-webview-nexus5X
android-webview-nexus6

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 8d5278293ca158a7bcf8d3a919a0082e36378cfc
  bad_revision : ce099e953eebf2a7244f69695f1b9e602c51a3db

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_other_cpu_time_per_frame/http___m.nytimes.com_

Revision             Result                      N
chromium@506286      0.140904 +- 0.00794709      6      good
chromium@506329      0.141884 +- 0.00799854      6      good
chromium@506350      0.142222 +- 0.00796599      6      good
chromium@506359      0.141494 +- 0.00575837      6      good
chromium@506371      0.477147 +- 0.0339986       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...m.nytimes.com. thread_times.simple_mobile_sites

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Hi hajimehoshi@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 : Hajime Hoshi
  Commit : f6af34a1a523e06a8ef371f21469050795924eb5
  Date   : Wed Oct 04 11:05:48 2017
  Subject: Add RendererSchedulerImpl::V8TaskQueue()

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_other_cpu_time_per_frame/http___m.nytimes.com_
  Change       : 148.62% | 0.197008842145 -> 0.489802673994

Revision             Result                      N
chromium@506316      0.197009 +- 0.0304847       6      good
chromium@506341      0.195399 +- 0.016735        6      good
chromium@506353      0.196857 +- 0.00917059      6      good
chromium@506359      0.197456 +- 0.00827861      6      good
chromium@506362      0.196093 +- 0.0152721       6      good
chromium@506363      0.192192 +- 0.0330208       6      good
chromium@506364      0.486796 +- 0.0151485       6      bad       <--
chromium@506365      0.489803 +- 0.0378288       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...m.nytimes.com. thread_times.simple_mobile_sites

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

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


For feedback, file a bug with component Speed>Bisection

 Issue 773023  has been merged into this issue.

 Issue 773687  has been merged into this issue.

FYI +haraken, +altimin

The fix was already reverted, but we're reland it again later.