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

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


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

chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : page_cycler_v2.basic_oopif
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.nationalgeographic.com_

Revision             Result                  N
chromium@484782      382.039 +- 427.11       21      good
chromium@484843      401.811 +- 450.649      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.nationalgeographic.com. page_cycler_v2.basic_oopif

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

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


For feedback, file a bug with component Speed>Bisection

This test has been decommissioned.