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

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


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

android-nexus5

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : cpu_time_percentage_avg/load_chrome/load_chrome_blank


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.chrome.blank system_health.common_mobile

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Michael Lippautz
  Commit : f46a92c2a8c716c6ad49ea61c4283bdffba3e52a
  Date   : Wed Oct 04 11:24:09 2017
  Subject: [heap] MC: Parallel marking for the atomic pause

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : serialize-array/serialize-array
  Change       : 36.62% | 31.9851666667 -> 43.6966666667

Revision                           Result                   N
chromium@506371                    31.9852 +- 0.5236        6      good
chromium@506407                    32.1687 +- 0.255713      6      good
chromium@506425                    31.9158 +- 0.341167      6      good
chromium@506425,v8@f46a92c2a8      43.8372 +- 4.112         6      bad       <--
chromium@506425,v8@22069a18b9      41.7722 +- 7.61855       6      bad
chromium@506426                    38.9293 +- 9.01671       6      bad
chromium@506427                    43.8982 +- 6.35158       6      bad
chromium@506428                    45.538 +- 6.23046        6      bad
chromium@506430                    44.5083 +- 6.10097       6      bad
chromium@506434                    44.0298 +- 4.16125       6      bad
chromium@506443                    43.6967 +- 10.7523       6      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.bindings

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

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


For feedback, file a bug with component Speed>Bisection