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

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


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

chromium-rel-mac11-pro
chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/FarsNews

Revision             Result                  N
chromium@500442      287.506 +- 60.6699      20      good
chromium@500507      285.411 +- 55.9371      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=FarsNews loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

Regression has recovered.