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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=401016bb6724b409dadb59a993c9953bc5ff2807806a810b5718c460ad920eb9


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

chromium-rel-mac-retina

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

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

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

Hi mlippautz@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 : Michael Lippautz
  Commit : a45048e20582e7fb1f1f5c7d4b77110dab1f9cba
  Date   : Thu Jul 20 14:05:02 2017
  Subject: [heap] Parallel Scavenge

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : API:duration_avg/browse_tech/browse_tech_discourse_infinite_scroll
  Change       : 18.09% | 99.4441666667 -> 117.430166667

Revision                           Result                  N
chromium@488730                    99.4442 +- 10.2537      6      good
chromium@488742                    99.4118 +- 4.90381      6      good
chromium@488745                    100.509 +- 9.32512      6      good
chromium@488745,v8@b23b8c088c      103.105 +- 16.4623      9      good
chromium@488745,v8@1084d20978      104.208 +- 13.6155      6      good
chromium@488745,v8@ecd06ed09f      102.059 +- 3.93292      6      good
chromium@488745,v8@a45048e205      121.835 +- 10.589       6      bad       <--
chromium@488745,v8@f24b6f96f8      120.414 +- 8.99614      6      bad
chromium@488745,v8@8ab48b6c04      120.046 +- 8.29116      6      bad
chromium@488746                    119.337 +- 12.6623      6      bad
chromium@488747                    119.177 +- 4.84625      6      bad
chromium@488748                    117.985 +- 6.10174      6      bad
chromium@488754                    117.179 +- 6.35583      6      bad
chromium@488777                    120.639 +- 8.38944      6      bad
chromium@488823                    117.43 +- 11.0558       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.tech.discourse.infinite.scroll v8.runtimestats.browsing_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973206640754147888


For feedback, file a bug with component Speed>Bisection

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

Hi ulan@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 : Ulan Degenbaev
  Commit : 176a2b24fb23a0c9a3bc9eec27f6445dbfa5ab27
  Date   : Wed Jul 19 13:04:47 2017
  Subject: [heap] Reland "[heap] Allow a minimum semi-space size of 512K."

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-scavenger_sum/browse_search/browse_search_google_india
  Change       : 17.05% | 10.0438333333 -> 11.7563333333

Revision                           Result                   N
chromium@488689                    10.0438 +- 1.19327       6      good
chromium@488745                    9.45517 +- 1.66123       6      good
chromium@488745,v8@ae9a2d38f3      9.59033 +- 1.42102       6      good
chromium@488745,v8@91c1a81d0e      9.12333 +- 3.03105       9      good
chromium@488745,v8@bb29f9a4d6      8.851 +- 1.92296         6      good
chromium@488745,v8@176a2b24fb      11.6857 +- 1.89586       6      bad       <--
chromium@488745,v8@7cfd0c249e      11.8307 +- 2.06916       6      bad
chromium@488745,v8@b23b8c088c      11.9407 +- 2.02536       6      bad
chromium@488746                    11.855 +- 1.42825        6      bad
chromium@488747                    12.7527 +- 0.854377      6      bad
chromium@488749                    12.0087 +- 1.24621       6      bad
chromium@488752                    12.5495 +- 1.64556       6      bad
chromium@488759                    12.1225 +- 1.81992       6      bad
chromium@488773                    12.0018 +- 2.10954       6      bad
chromium@488800                    11.7563 +- 1.48521       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.search.google.india v8.runtimestats.browsing_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973199694178052288


For feedback, file a bug with component Speed>Bisection

 Issue 747807  has been merged into this issue.

 Issue 747807  has been merged into this issue.

 Issue 748393  has been merged into this issue.

 Issue 748461  has been merged into this issue.

 Issue 748449  has been merged into this issue.

 Issue 747969  has been merged into this issue.

 Issue 748534  has been merged into this issue.

 Issue 748541  has been merged into this issue.

 Issue 748532  has been merged into this issue.

Parallel scavenge regressions are "won't fix" because of tradeoff.

The "Allow a minimum semi-space size of 512K" regressions are fixed by revert of the CL.