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

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


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

chromium-rel-mac11

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

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

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-step_sum/browse_social/browse_social_twitter

Revision             Result                  N
chromium@455787      174.845 +- 130.322      21      good
chromium@455929      185.66 +- 129.653       21      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=browse.social.twitter v8.runtimestats.browsing_desktop

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

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


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

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

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

Suspected Commit
  Author : Michael Hablich
  Commit : 7c3936c67a6361371d9a00d83e2c03ecc603ce76
  Date   : Thu Mar 09 08:05:42 2017
  Subject: Version 5.9.34.1 (Turn on I+TF)

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-step_sum/browse_social/browse_social_twitter
  Change       : 92.88% | 102.745166667 -> 198.1745

Revision                           Result                  N
chromium@455000                    102.745 +- 52.4817      6       good
chromium@455550                    112.706 +- 68.1799      6       good
chromium@455688                    112.383 +- 85.314       9       good
chromium@455706                    108.946 +- 65.4752      6       good
chromium@455715                    101.741 +- 54.5008      6       good
chromium@455719                    110.05 +- 120.323       14      good
chromium@455719,v8@7c3936c67a      172.59 +- 59.8466       9       bad       <--
chromium@455719,v8@fbffc377e3      188.416 +- 51.9076      6       bad
chromium@455720                    204.175 +- 55.1495      6       bad
chromium@455721                    166.033 +- 98.9689      14      bad
chromium@455723                    192.459 +- 87.4749      9       bad
chromium@455757                    188.408 +- 122.902      9       bad
chromium@455825                    184.105 +- 74.9526      9       bad
chromium@456100                    198.175 +- 44.7319      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=browse.social.twitter v8.runtimestats.browsing_desktop

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

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


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

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