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

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


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

chromium-rel-win10

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

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

Suspected Commit
  Author : meade
  Commit : 3a001533b29c0fe28f2354285b2c2ac8d57d8ce6
  Date   : Mon Mar 13 05:26:20 2017
  Subject: Un-DCHECK-guard ThreadRestrictionVerifier for strings.

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : page_cycler_v2_site_isolation.basic_oopif
  Metric       : timeToFirstContentfulPaint_avg/pcv1-warm/http___booking.com
  Change       : 8.42% | 93.7355714286 -> 99.6438333367

Revision             Result                  N
chromium@456320      93.7356 +- 18.6824      14      good
chromium@456322      93.047 +- 10.4348       9       good
chromium@456323      99.2606 +- 18.6345      14      bad       <--
chromium@456327      98.5005 +- 16.2646      14      bad
chromium@456333      96.7346 +- 9.77247      9       bad
chromium@456345      99.6438 +- 9.12941      6       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...booking.com page_cycler_v2_site_isolation.basic_oopif

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

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


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