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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg5sGa8gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg5u_erQkM


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/8977267176826101664

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

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

Revision             Result                  N
chromium@477238      497.877 +- 335.645      21      good
chromium@477300      486.479 +- 216.429      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=TheOnion loading.desktop

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

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


| 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/8977261034347353424

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

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

Revision             Result                  N
chromium@477238      523.764 +- 376.119      21      good
chromium@477300      518.858 +- 363.549      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=TheOnion loading.desktop

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

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


| 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!

The regression occurs over a wider range. I'm going to expand the range for the bisect. If it's correct though, not sure what can be done 2 months later.

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

=== Auto-CCing suspected CL author mek@chromium.org ===

Hi mek@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : mek
  Commit : c8e2b27f71c6792fa1072fa98a22c111ad229090
  Date   : Tue Jun 06 23:18:28 2017
  Subject: Switch to mojo localstorage backend by default.

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-cold/IMDB
  Change       : 31.26% | 259.506 -> 340.623666666

Revision             Result                  N
chromium@476956      259.506 +- 46.267       6      good
chromium@477287      266.206 +- 50.1446      6      good
chromium@477453      275.23 +- 58.2447       6      good
chromium@477456      269.023 +- 59.2181      6      good
chromium@477457      266.362 +- 56.6431      6      good
chromium@477458      333.696 +- 21.6826      6      bad       <--
chromium@477459      334.433 +- 14.6454      6      bad
chromium@477464      345.916 +- 49.9336      6      bad
chromium@477474      335.4 +- 21.0626        6      bad
chromium@477495      336.462 +- 33.0715      6      bad
chromium@477536      348.822 +- 52.0328      6      bad
chromium@477618      340.624 +- 45.5846      6      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=IMDB loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

 Issue 731676  has been merged into this issue.

mek: any update on this? looks like a pretty big loading regression. adding test owner kouhei so he can help with priority.