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

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


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

chromium-rel-win10

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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : frame_times/Docs  (1 open document tab)

Revision             Result                  N
chromium@470517      17.9813 +- 1.42197      21      good
chromium@470541      18.0091 +- 1.69937      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 --story-filter=Docs...1.open.document.tab. smoothness.top_25_smooth

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

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


| 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/8979880794611913648

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : frame_times/Docs  (1 open document tab)

Revision             Result                  N
chromium@470517      18.0578 +- 1.27985      21      good
chromium@470541      17.8492 +- 1.68958      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 --story-filter=Docs...1.open.document.tab. smoothness.top_25_smooth

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

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


| 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/8979788034879816096

Bisecting again with cleaner metric.

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

Suspected Commit
  Author : yhirano
  Commit : 91088a195969f5af61f404c9f02edc622cbe373a
  Date   : Wed May 10 05:49:31 2017
  Subject: Add Field Trial Testing Configuration for MojoLoading

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : mean_input_event_latency/Docs  (1 open document tab)
  Change       : 19.13% | 18.9782222222 -> 22.608

Revision             Result                  N
chromium@470480      18.9782 +- 3.94471      9      good
chromium@470487      18.3372 +- 1.2816       6      good
chromium@470489      18.0205 +- 1.66244      6      good
chromium@470490      22.4647 +- 1.33797      6      bad       <--
chromium@470493      22.6462 +- 1.17793      6      bad
chromium@470506      22.645 +- 0.698664      6      bad
chromium@470531      22.608 +- 0.544496      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=Docs...1.open.document.tab. smoothness.top_25_smooth

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

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


| 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!