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

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


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

chromium-rel-win8-dual

Previous bisects were timing out.

Kicked off a new bisect here:
https://chromeperf.appspot.com/buildbucket_job_status/9013044724639259472

with a timeout of 60 minutes.

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The regression is still here. Kicked off another bisect.

This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@388341  41.2461  0.102187   5  good
chromium@388356  41.2255  0.0582128  5  good
chromium@388364  41.6506  0.0287693  5  bad
chromium@388366  41.6505  0.0262686  5  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 605099

Test Command: .\src\out\Release\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu
Test Metric: CastV2Performance_gpu_novsync_24fps/time_between_captures
Relative Change: 0.98%
Score: 0

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


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

| 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/8999613674108189920

Looks like the regression is still there but the bisect didn't find anything. Kicked another one to try to find a culprit.

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@388341  41.2386  0.0621262  5  good
chromium@388356  41.2646  0.110027   5  good
chromium@388364  41.6571  0.025151   5  bad
chromium@388366  41.6514  0.0082355  5  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 605099

Test Command: .\src\out\Release\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu
Test Metric: CastV2Performance_gpu_novsync_24fps/time_between_captures
Relative Change: 1.00%
Score: 0

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


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

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

perf sheriff fixit: unsetting owner for bugs owned by perf sheriffs to clarify that they are triaged by a rotation.

Resolving as the new behavior is actually better! :)

This is because, for a 24 FPS capture test, the average time between captures should be 1/24 seconds == 41.67 ms. Before the "regression point" we were measuring 41.2, and afterwards we are measuring 41.65 ms. That's good!