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

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


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

linux-release

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

Is it possible to associate https://chromeperf.appspot.com/buildbucket_job_status/8973808061042684288 also with this?

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : page_cycler_v2.basic_oopif
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___www.cnn.com

Revision             Result                  N
chromium@486457      480.358 +- 225.498      21      good
chromium@486537      455.277 +- 36.6152      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.cnn.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/8973799699429620000


For feedback, file a bug with component Speed>Bisection

The bisect mentioned in #3 bisects to https://chromium.googlesource.com/chromium/src.git/+/6edbb267b6d43303d08e758ff63f941df5c8ff7f%5E%21/#F0 (if I'm reading it right) but both graphs seem to have recovered in the mean time.