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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6rD2oAkM


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

chromium-rel-win7-gpu-intel

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame

Revision             Result                     N
chromium@471245      0.684965 +- 0.0700625      21      good
chromium@471282      0.678379 +- 0.0450696      21      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 thread_times.tough_scrolling_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979245986658755120

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6734619908505600


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

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

Suspected Commit
  Author : Yutaka Hirano
  Commit : 823d5c738187627cbe218f01ddac6f383bcaaba8
  Date   : Fri May 12 09:29:18 2017
  Subject: Set URLResponseBodyConsumer::kMaxNumConsumedBytesInTask to 32K

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame
  Change       : 2.87% | 0.671447101267 -> 0.655171459194

Revision             Result                     N
chromium@471245      0.671447 +- 0.0359816      14      good
chromium@471256      0.689441 +- 0.0242845      6       good
chromium@471257      0.656185 +- 0.0237603      6       bad       <--
chromium@471258      0.673074 +- 0.0189343      9       bad
chromium@471260      0.666857 +- 0.020945       6       bad
chromium@471264      0.662462 +- 0.0510857      14      bad
chromium@471282      0.655171 +- 0.0328162      9       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 thread_times.tough_scrolling_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979208867345302368

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6734619908505600


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!