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

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


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

chromium-rel-win10

===== BISECT JOB RESULTS =====
Status: completed


=== 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.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@381142         899.933333  53.323257   12          good
chromium@381155         877.616667  93.641267   12          bad

Bisect job ran on: winx64_10_perf_bisect
Bug ID: 595053

Test Command: python src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --also-run-disabled-tests startup.cold.blank_page
Test Metric: messageloop_start_time/messageloop_start_time
Relative Change: 5.96%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/466
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9018101374485914304


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

previous bisect job aborted, re-kicked bisect with modified range.

===== BISECT JOB RESULTS =====
Status: completed


=== 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.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@381120         1095.866667 92.693016   12          good
chromium@381175         998.566667  116.708645  12          bad

Bisect job ran on: winx64_10_perf_bisect
Bug ID: 595053

Test Command: python src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --also-run-disabled-tests startup.cold.blank_page
Test Metric: messageloop_start_time/messageloop_start_time
Relative Change: 12.58%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/470
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017517956178233504


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

I think this test may be bimodal? On the graph I can see both ToT and ref build jumping between ~700ms and ~1000ms