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

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


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

win-zenbook

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@381759         278.781467  71.687655   18          good
chromium@381782         269.407178  67.206482   18          bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 596065

Test Command: python src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --also-run-disabled-tests smoothness.key_desktop_move_cases
Test Metric: input_event_latency_discrepancy/input_event_latency_discrepancy
Relative Change: 3.07%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/106
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017844369936180176


| 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 label Cr-Tests-AutoBisect.  Thank you!

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@381759         277.879808  60.032477   18          good
chromium@381782         285.110942  74.932821   18          bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 596065

Test Command: python src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --also-run-disabled-tests smoothness.key_desktop_move_cases
Test Metric: input_event_latency_discrepancy/input_event_latency_discrepancy
Relative Change: 25.81%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/107
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017838227221462640


| 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 label Cr-Tests-AutoBisect.  Thank you!

Kicked off another pair of bisects, including a stdev bisect.

Kicked off https://chromeperf.appspot.com/buildbucket_job_status/9016893322506409712 with a wider range as well. Some of the previous bisects seem hit failing tests, not sure this will succeed.

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : SimpleCache: Add fieldtrial testing information.
Author  : gavinp
Commit description:
  
This came up as a warning for a new finch trial advancing these to
beta.

R=asvitkine
BUG=490029

Review URL: https://codereview.chromium.org/1790483003

Cr-Commit-Position: refs/heads/master@{#381718}
Commit  : 27d70c8f346bef4e1bc60acfab744dbcb5586e59
Date    : Thu Mar 17 15:45:07 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@381686         175.484475  20.041024   8           good
chromium@381712         176.022188  18.147904   8           good
chromium@381717         186.225667  24.358745   12          good
chromium@381718         323.633919  72.005308   8           bad         <-
chromium@381719         293.10007   108.614825  5           bad
chromium@381720         288.221267  76.396115   12          bad
chromium@381723         262.518756  67.799329   8           bad
chromium@381734         282.29353   68.089106   5           bad
chromium@381782         281.777881  86.31662    8           bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 596065

Test Command: python src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --also-run-disabled-tests smoothness.key_desktop_move_cases
Test Metric: input_event_latency_discrepancy/input_event_latency_discrepancy
Relative Change: 69.53%
Score: 90.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/124
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016893322506409712


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=596065

| 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 Tests>AutoBisect.  Thank you!

gavinp@, your change shouldn't have any performance impact, should it? There are a few bisects that are pointing at your change.