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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrNnK5woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7NCTrgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrIGwtQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzJOalggM


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

chromium-rel-win10
chromium-rel-win7-x64-dual

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

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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : page_cycler_v2.intl_hi_ru
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___apeha.ru_

Revision             Result                  N
chromium@459527      533.671 +- 821.027      21      good
chromium@459639      501.399 +- 375.427      20      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...apeha.ru. page_cycler_v2.intl_hi_ru

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

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


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

noise