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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg08KTuAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg04OvsAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg0_vZsAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgk6_75QsM


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

win-zenbook

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

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@430593  890.066  182.384  27  good
chromium@430665  892.319  100.012  27  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 664103

Test Command: 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.google.com.hk..q..E9.82.84.E6.8F.90.E4.BE.9B.fp.c44d333e710cb480 page_cycler_v2.intl_ja_zh
Test Metric: timeToFirstContentfulPaint_avg/pcv1-cold/http___www.google.com.hk__q_%E9%82%84%E6%8F%90%E4%BE%9B_fp_c44d333e710cb480
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/592
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8996335380089683552


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5832131098443776

| 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 Tests>AutoBisect.  Thank you!

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@430593  897.69   241.581  27  good
chromium@430665  894.948  200.083  27  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 664103

Test Command: 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.google.com.hk..q..E9.82.84.E6.8F.90.E4.BE.9B.fp.c44d333e710cb480 page_cycler_v2.intl_ja_zh
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-cold/http___www.google.com.hk__q_%E9%82%84%E6%8F%90%E4%BE%9B_fp_c44d333e710cb480
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/595
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8996285288552277456


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6472945453498368

| 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 Tests>AutoBisect.  Thank you!

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@430593  1049.33  409.484  27  good
chromium@430665  1042.11  363.234  27  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 664103

Test Command: 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.google.com.hk..q..E9.82.84.E6.8F.90.E4.BE.9B.fp.c44d333e710cb480 page_cycler_v2.intl_ja_zh
Test Metric: timeToFirstContentfulPaint_avg/pcv1-cold/http___www.google.com.hk__q_%E9%82%84%E6%8F%90%E4%BE%9B_fp_c44d333e710cb480
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/599
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8996212148855302208


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6368935975321600

| 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 Tests>AutoBisect.  Thank you!

lgtm with the exception of "Relative change: None", for which I filed  bug 664743 . I'll mark this one fixed.