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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : blink_perf.shadow_dom
  Metric       : v0-shadow-reprojection/v0-shadow-reprojection

Revision             Result                 N
chromium@510668      20.4276 +- 1.3704      21      good
chromium@510708      20.271 +- 2.48226      21      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.shadow_dom

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

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


For feedback, file a bug with component Speed>Bisection

This recovered.