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

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


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

chromium-rel-win7-gpu-intel

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

=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Step('Bisecting revision.Post bisect results (10)') failed with return_code 1


Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : jetstream
  Metric       : Score/Score

Revision                           Result                   N
chromium@492380                    182.444 +- 0.902671      6      good
chromium@492423                    181.889 +- 0.7698        6      good
chromium@492434                    182.222 +- 0.902671      6      good
chromium@492440                    182.056 +- 0.871355      6      good
chromium@492443                    181.722 +- 1.09713       6      good
chromium@492444                    181.778 +- 0.7698        6      good
chromium@492444,v8@a7a166e30c      182.056 +- 1.09713       6      good
chromium@492444,v8@ceb55494bd      181.778 +- 0.608581      6      good
chromium@492444,v8@864837ff3c      179.056 +- 1.6611        6      bad
chromium@492445                    178.389 +- 1.6611        6      bad
chromium@492466                    178.778 +- 1.01835       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 jetstream

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : feb3ee40d03137ffcc2be98a01f6ea936cdf45e1
  Date   : Mon Aug 07 16:21:24 2017
  Subject: [heap] Disable parallel scavenge.

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : jetstream
  Metric       : Score/Score
  Change       : 2.10% | 182.222222222 -> 178.388888889

Revision                           Result                   N
chromium@492380                    182.222 +- 1.12217       6      good
chromium@492423                    182.611 +- 0.732828      6      good
chromium@492434                    182.0 +- 0.942809        6      good
chromium@492440                    182.389 +- 1.09713       6      good
chromium@492443                    182.5 +- 1.13039         6      good
chromium@492444                    182.056 +- 1.2838        6      good
chromium@492444,v8@a7a166e30c      181.889 +- 1.46566       6      good
chromium@492444,v8@ceb55494bd      182.0 +- 0.816497        6      good
chromium@492444,v8@feb3ee40d0      178.056 +- 1.7267        6      bad       <--
chromium@492444,v8@864837ff3c      178.5 +- 1.74801         6      bad
chromium@492445                    178.167 +- 1.92931       6      bad
chromium@492466                    178.389 +- 0.871355      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 jetstream

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

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


For feedback, file a bug with component Speed>Bisection