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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=6a5c553b298ff54aa8b3727f6d10f518091a463f501bee3afc2f5d9f772a8bd1


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

chromium-rel-win7-gpu-nvidia

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

ANGLE roll:

https://chromium.googlesource.com/angle/angle.git/+log/a60d356..000dab8

Suspecting maybe "D3D11: Lazy robust resource init"

https://chromium-review.googlesource.com/576058

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

Hi jmadill@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Jamie Madill
  Commit : 05b35b210ef3dcdf7e3260d192ce51b602b6f3a7
  Date   : Tue Oct 03 14:18:13 2017
  Subject: D3D11: Lazy robust resource init.

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : angle_perftests
  Metric       : DrawCallPerf_gl_null/score
  Change       : 10.87% | 182615.833333 -> 162756.833333

Revision                              Result                 N
chromium@506862                       182616 +- 2038.6       6      good
chromium@506884                       182705 +- 4698.27      6      good
chromium@506895                       182241 +- 5508.35      6      good
chromium@506901                       181950 +- 3648.81      6      good
chromium@506902                       182812 +- 1043.53      6      good
chromium@506902,angle@05b35b210e      162499 +- 1271.83      6      bad       <--
chromium@506902,angle@8c5b31c29d      164868 +- 1215.48      6      bad
chromium@506902,angle@09cd47779d      164297 +- 4144.46      6      bad
chromium@506902,angle@7e7f7d25b8      160585 +- 1155.54      6      bad
chromium@506902,angle@d03a849d79      165635 +- 2021.53      6      bad
chromium@506903                       162628 +- 2491.03      6      bad
chromium@506904                       162717 +- 1186.16      6      bad
chromium@506906                       161920 +- 4112.7       6      bad
chromium@506949                       162757 +- 709.114      6      bad

To Run This Test
  .\src\out\Release_x64\angle_perftests.exe --test-launcher-print-test-stdio=always --test-launcher-jobs=1

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8966024614180615488


For feedback, file a bug with component Speed>Bisection

Geoff would you want to look at this?