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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9Z2osAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtbXY-QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9bbR-gsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9YvEoAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9ZmLtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9arT7goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgjfiBqAoM


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

chromium-rel-win10
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win8-dual

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

=== Auto-CCing suspected CL author jbauman@chromium.org ===

Hi jbauman@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Add 1 second delay before gestures in smoothness.top_25_smooth
Author  : jbauman
Commit description:
  
With GPU rasterization there's a one-time startup cost of doing shader
compiles for skia. The tests were starting their gestures almost
immediately after load, so they were sometimes forced to wait for the
shader compiles to happen before the first gesture.

This test was intended to test scrolling smoothness, not time to first
paint, so adding a delay makes them more consistent. In the real world
these shaders are most likely cached on disk or in memory, so any load
after the browser was running a while should be better.

BUG= 648644 

Review-Url: https://codereview.chromium.org/2354243004
Cr-Commit-Position: refs/heads/master@{#423886}
Commit  : 7ac9b1b7052cc76fa7b3fef51d2dc447f55991d3
Date    : Fri Oct 07 16:53:36 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@423849  16.169   0.0604051  5  good
chromium@423870  16.2295  0.0431473  5  good
chromium@423881  16.2194  0.0635404  5  good
chromium@423884  16.2271  0.034932   5  good
chromium@423885  16.1921  0.0673319  5  good
chromium@423886  16.7291  0.0238951  5  bad    <--
chromium@423891  16.723   0.0265571  5  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 654223

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: frame_times/LinkedIn
Relative Change: 3.43%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2232
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999350848449007808


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

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

jbauman@, it looks like this was intended and is not an actual performance regression, right?