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

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


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

chromium-rel-win10

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

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

Suspected Commit
  Author : yhirano
  Commit : 91088a195969f5af61f404c9f02edc622cbe373a
  Date   : Wed May 10 05:49:31 2017
  Subject: Add Field Trial Testing Configuration for MojoLoading

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : page_cycler_v2.basic_oopif
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.fifa.com_
  Change       : 15.73% | 321.751555555 -> 372.353666668

Revision             Result                  N
chromium@470445      321.752 +- 36.4191      9       good
chromium@470481      309.849 +- 50.7607      14      good
chromium@470486      327.975 +- 335.613      14      good
chromium@470488      315.646 +- 22.2587      6       good
chromium@470489      316.43 +- 27.1758       6       good
chromium@470490      373.864 +- 125.341      14      bad       <--
chromium@470499      366.889 +- 168.769      14      bad
chromium@470517      372.354 +- 128.473      9       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.fifa.com. page_cycler_v2.basic_oopif

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

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


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

tzik@, can you look into this issue?

 Issue 721293  has been merged into this issue.

Gentle ping on this tzik@, would like to try and get this moved off the sheriff backlog. It looks like the graph never recovered https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqsHXvgoM

IIRC this happened at the same time as a bunch of other regressions/improvements 
due to mojo loading being turned on. Maybe we you link to the existing analysis here?