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

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


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

chromium-rel-win7-gpu-nvidia

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

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

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

Hi jmadill@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 : D3D11: Get driver version from DXGI adapter.
Author  : Jamie Madill
Commit description:
  
This is a simpler and more portable design. Thanks for Austin from MS.

BUG= angleproject:1452 

Change-Id: I93e8f3fc61107f13c4b2c1cf7fbaf2bb7ccdfafb
Reviewed-on: https://chromium-review.googlesource.com/363041
Reviewed-by: Austin Kinross <aukinros@microsoft.com>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Commit  : 64ae9952823b4060120dc4fe8451476b564faf81
Date    : Thu Jul 28 01:48:52 2016


===== TESTED REVISIONS =====
Revision                          Mean     Std Dev     N  Good?
chromium@408972                   0.0      0.0         5  good
chromium@408978                   0.0      0.0         5  good
chromium@408981                   0.0      0.0         5  good
chromium@408983                   0.0      0.0         5  good
chromium@408983,angle@ee0fac3fa5  0.0      0.0         5  good
chromium@408983,angle@64ae995282  1.00664  0.00494795  5  bad    <--
chromium@408984                   1.00938  0.00797521  5  bad
chromium@408994                   1.00573  0.00566941  5  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 633590

Test Command: .\src\out\Release_x64\angle_perftests.exe --test-launcher-print-test-stdio=always --test-launcher-jobs=1
Test Metric: EGLInitialize_run/InitResources
Relative Change: Zero to non-zero
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1769
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005428052719221584


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

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

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


===== SUSPECTED CL(s) =====
Subject : D3D11: Get driver version from DXGI adapter.
Author  : Jamie Madill
Commit description:
  
This is a simpler and more portable design. Thanks for Austin from MS.

BUG= angleproject:1452 

Change-Id: I93e8f3fc61107f13c4b2c1cf7fbaf2bb7ccdfafb
Reviewed-on: https://chromium-review.googlesource.com/363041
Reviewed-by: Austin Kinross <aukinros@microsoft.com>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Commit  : 64ae9952823b4060120dc4fe8451476b564faf81
Date    : Thu Jul 28 01:48:52 2016


===== TESTED REVISIONS =====
Revision                          Mean     Std Dev     N  Good?
chromium@408972                   0.0      0.0         5  good
chromium@408978                   0.0      0.0         5  good
chromium@408981                   0.0      0.0         5  good
chromium@408983                   0.0      0.0         5  good
chromium@408983,angle@ee0fac3fa5  0.0      0.0         5  good
chromium@408983,angle@64ae995282  1.00051  0.00114965  5  bad    <--
chromium@408984                   1.0031   0.00462845  5  bad
chromium@408994                   1.00513  0.00722288  5  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 633590

Test Command: .\src\out\Release_x64\angle_perftests.exe --test-launcher-print-test-stdio=always --test-launcher-jobs=1
Test Metric: EGLInitialize_run/InitResources
Relative Change: Zero to non-zero
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1770
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005428046670081472


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

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

Good job bisect, that seems like a likely CL. Unfortunately this is necessary and the regression is small, so there's not much we can do at the moment.