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

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


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

chromium-rel-mac11

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

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

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : page_cycler_v2_site_isolation.basic_oopif
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___www.nationalgeographic.com_

Revision             Result                  N
chromium@495075      587.661 +- 117.399      18      good
chromium@495131      597.534 +- 141.251      19      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_site_isolation.basic_oopif

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

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


For feedback, file a bug with component Speed>Bisection

This benchmark has been removed.