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

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


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

chromium-rel-mac-retina

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-cold/Naver

Revision             Result                  N
chromium@495450      848.692 +- 1679.8       21      good
chromium@495510      791.545 +- 1692.61      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=Naver loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

This is just two pages on a single device. Bisect can't repro. Not sure what else can be done here.