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

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


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

chromium-rel-mac11

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

Not sure what happened to the bisect, kicking another.

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

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-cold/Orange

Revision             Result                  N
chromium@497662      128.103 +- 56.1493      21      good
chromium@497695      124.477 +- 65.8248      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=Orange loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

Bisect can't reproduce.