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

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


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

chromium-rel-win7-gpu-intel
chromium-rel-win8-dual

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

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

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

Revision             Result                  N
chromium@452261      10.3309 +- 12.4253      21      good
chromium@452407      11.0064 +- 13.5669      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/8986734235835157440

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


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

Re-running bisect. It's not clear (due to lack of "ref" datasets) whether the bot environment is the cause, or if there really is a performance regression here.

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

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

Revision             Result                  N
chromium@452261      8.25638 +- 11.8902      21      good
chromium@452407      9.10157 +- 10.2554      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/8986718734197618528

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


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

Seems like a tiny change, well within the long term norm; and smaller than the standard deviation of the measurements. I don't see anything actionable here.