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

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


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

chromium-rel-win7-gpu-intel

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

===== 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     Std Dev     N   Good?
chromium@407499  16.6668  0.00460889  18  good
chromium@407529  16.6649  0.00158938  18  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 631402

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.tough_webgl_cases
Test Metric: mean_frame_time/http___webglsamples.org_aquarium_aquarium.html
Relative Change: 0.01%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1042
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006084646298251120


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

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

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

===== 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     Std Dev     N   Good?
chromium@407499  16.6663  0.00187257  18  good
chromium@407529  16.6671  0.00568682  18  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 631402

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.tough_webgl_cases
Test Metric: mean_frame_time/http___webglsamples.org_aquarium_aquarium.html
Relative Change: 0.01%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1043
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006070606433662432


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

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

Reassigning to test owner (kbr@).
Didn't manage to get anything out of the bisect and I'm going to be OOO soon. Not sure what else I can do here (I just kicked another bisect but I don't have great expectations at this point)
The regression seems pretty sharp on the waterfall.

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

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


===== SUSPECTED CL(s) =====
Subject : Enable Per-Monitor DPI Unless Explicitly Disabled
Author  : robliao
Commit description:
  
                   Per Monitor DPI Settings
Flags              Before             After
No Flags           Disabled           Enabled
Enable             Enabled            Enabled
Enable + Disabled  Disabled           Disabled
Disabled           Disalbed           Disabled

BUG= 426656 

Review-Url: https://codereview.chromium.org/2175693004
Cr-Commit-Position: refs/heads/master@{#407508}
Commit  : 23364eecc5d1bb1770f8c22a7c0a320154e3eac7
Date    : Mon Jul 25 17:55:26 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@407505  19.7554  0.222538   5  good
chromium@407507  19.8974  0.263435   5  good
chromium@407508  22.8077  0.229557   5  bad    <--
chromium@407509  23.4645  0.421818   5  bad
chromium@407512  23.2211  0.397075   5  bad
chromium@407520  22.9464  0.0740375  5  bad
chromium@407537  23.0482  0.318459   5  bad

Bisect job ran on: winx64_10_perf_bisect
Bug ID: 631402

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.tough_filters_cases
Test Metric: frame_times/http___letmespellitoutforyou.com_samples_svg_filter_terrain.svg
Relative Change: 16.67%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/618
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005787908084045408


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

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