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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjrWwuQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgju28tQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjub7uQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjuadqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjoa65ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjqnZowkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjoa6pgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjqmyrQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjp6JpwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjs2CowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjobwqgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjun6tgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjtePpQoM


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

chromium-rel-mac-retina
chromium-rel-mac11

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/Yandex

Revision             Result                N
chromium@480312      54.637 +- 16.222      21      good
chromium@480349      63.821 +- 51.454      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=Yandex loading.desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976253123019503536

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5330566351683584


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/Yandex

Revision             Result                  N
chromium@480312      54.0386 +- 15.3307      21      good
chromium@480349      65.7642 +- 55.3644      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=Yandex loading.desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976245594334805072

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5330566351683584


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

No ref build, and bisects can't reproduce, and only on one bot. Hardware change?