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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglK-h-ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg5I-L8woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1Jj6oQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglN_CtwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglP63-goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1MjAqwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglL3S6AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglPuGqQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1LLXrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglPuRuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglKKeqwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1NCB-QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg5I-s9QkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1JTDvQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglLet6AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglNbo5QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1JbQpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1PTvpwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglNKroQsM


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

android-nexus6
android-webview-nexus6
chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-pro
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win8-dual

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

=== Auto-CCing suspected CL author csharrison@chromium.org ===

Hi csharrison@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : csharrison
  Commit : 279edadbd6962b7afa97c166896ae69ceb797da4
  Date   : Mon Mar 06 17:05:49 2017
  Subject: Turn off LazyParseCSS on trybots for now

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : page_cycler_v2.basic_oopif
  Metric       : timeToFirstContentfulPaint_avg/pcv1-warm/http___booking.com
  Change       : 17.18% | 89.5266666661 -> 104.905666659

Revision             Result                   N
chromium@454739      89.5267 +- 1.33644       6      good
chromium@454875      90.7652 +- 0.953932      6      good
chromium@454877      91.3972 +- 1.42509       6      good
chromium@454878      90.9803 +- 1.49672       6      good
chromium@454879      106.316 +- 2.4592        6      bad       <--
chromium@454882      108.049 +- 6.34273       6      bad
chromium@454889      104.917 +- 1.973         6      bad
chromium@454903      104.343 +- 1.98573       6      bad
chromium@454930      105.948 +- 2.65241       6      bad
chromium@454985      104.906 +- 2.01534       6      bad

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

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

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


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

Yes, the experiment is cool and improves page load time, but we are pausing it due to memory concerns. See  issue 692932 .

Ha! Bisect doesn't tie things together and we must've missed doing this bisect at the time. Sorry for the noise and good luck!