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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghsmI_AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-ryKkwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-o_QpAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghtmQsAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqX6pQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-svRtQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghuDT8AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghpaAtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghtKwuwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghuLhsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghsaJtgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqDCvQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqKu6woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-tWt-QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-pH5hAoM


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

chromium-rel-mac11
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-intel
chromium-rel-win8-dual
linux-release
win-high-dpi

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : first_gesture_scroll_update_latency/LinkedIn

Revision             Result                N
chromium@474916      5.644 +- 5.72715      5      good
chromium@475003      6.357 +- 4.03899      2      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=LinkedIn smoothness.top_25_smooth

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

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


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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : first_gesture_scroll_update_latency/LinkedIn

Revision             Result                  N
chromium@474916      6.72343 +- 6.97635      7      good
chromium@475003      6.47033 +- 9.33269      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=LinkedIn smoothness.top_25_smooth

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

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


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

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

Suspected Commit
  Author : samans
  Commit : f26257b9ee4b7e722cc05468ceecbcf3f920be22
  Date   : Fri May 26 16:37:45 2017
  Subject: Send BeginFrames for the renderer using Mojo

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : queueing_durations/queueing_durations
  Change       : 8.09% | 0.105062387567 -> 0.11355804168

Revision             Result                      N
chromium@474979      0.105062 +- 0.00234866      6      good
chromium@475015      0.104531 +- 0.00307937      6      good
chromium@475024      0.103606 +- 0.00237954      6      good
chromium@475029      0.103794 +- 0.00141339      6      good
chromium@475030      0.112732 +- 0.00330049      6      bad       <--
chromium@475031      0.114386 +- 0.00093304      6      bad
chromium@475033      0.112711 +- 0.00359049      6      bad
chromium@475051      0.113347 +- 0.00344452      6      bad
chromium@475122      0.113558 +- 0.00142132      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 scheduler.tough_scheduling_cases

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

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


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