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

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


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

chromium-rel-win7-gpu-nvidia

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : angle_perftests
  Metric       : LinkProgram_gl/score

Revision             Result                  N
chromium@512503      1662.62 +- 105.579      21      good
chromium@513098      1659.76 +- 142.091      21      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/8964039571500999504


For feedback, file a bug with component Speed>Bisection

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 6d0fbe3096a8e2eef6c6e368e51f61e4a6fbd2b4
  bad_revision : 9a12266c63aeaacaa823e4956963f2980c65ac0f

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : angle_perftests
  Metric       : Bindings_gl_100_objects_allocated_every_iteration/score

Revision             Result                  N
chromium@512503      123.143 +- 5.15475      21      good
chromium@512506      123.5 +- 1.22474        6       good
chromium@512507      122.0 +- 1.41421        6       bad
chromium@512508      121.778 +- 2.74874      9       bad
chromium@512513      121.444 +- 2.86744      9       bad
chromium@512522      122.0 +- 2.82843        9       bad
chromium@512541      120.833 +- 3.85141      6       bad
chromium@512578      121.286 +- 6.07101      14      bad
chromium@512653      122.429 +- 3.89138      21      bad
chromium@512801      122.071 +- 4.3507       14      bad
chromium@513098      122.0 +- 4.69042        14      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/8964011498722640288


For feedback, file a bug with component Speed>Bisection

Most likely related to the driver upgrade in issue 712469.