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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjPb5kAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjOKgsgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9NTC4wsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9PuZkgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjOazvQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9Lu_lAgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9Lu_5AsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjIjA4gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9NTC4wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9J-W5wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjO_LvgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjOyotQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjOjfqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjJvtpwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9KaC7QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9Lng1goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjOblrAkM


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

chromium-rel-mac11-air
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-x64-dual
chromium-rel-win8-dual

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

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

Suspected Commit
  Author : sugoi
  Commit : 842efc6922b0cd66febd6f36f04318ebf396c184
  Date   : Tue Mar 14 18:10:39 2017
  Subject: Moving SwiftShader from component to bundled library

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : startup.warm.blank_page
  Metric       : foreground_tab_request_start/foreground_tab_request_start
  Change       : 313.89% | 2635.0 -> 10906.0

Revision             Result                  N
chromium@456705      2635.0 +- 138.167       6      good
chromium@456738      1379.67 +- 658.094      6      good
chromium@456754      1361.0 +- 462.815       6      good
chromium@456762      1358.83 +- 609.075      6      good
chromium@456763      1490.67 +- 641.739      6      good
chromium@456764      10919.3 +- 224.262      6      bad       <--
chromium@456766      10896.3 +- 66.2973      6      bad
chromium@456770      10922.5 +- 160.273      6      bad
chromium@456834      10906.0 +- 135.573      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=2 --also-run-disabled-tests startup.warm.blank_page

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

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


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