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

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


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

android-nexus5
android-nexus5X
android-one
chromium-rel-win8-dual
linux-release

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

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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 6bb1d47e6e82f75ead36cdab209afc5dafa8329c
  Date   : Tue Nov 07 13:11:10 2017
  Subject: [heap] Re-enable concurrent marking.

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.tough_compositor_cases
  Metric       : tasks_per_frame_other/tasks_per_frame_other
  Change       : 19.08% | 0.189414311348 -> 0.225562611125

Revision                           Result                      N
chromium@514613                    0.189414 +- 0.00541699      6      good
chromium@514629                    0.189459 +- 0.00605259      6      good
chromium@514637                    0.188709 +- 0.00425783      6      good
chromium@514641                    0.189756 +- 0.00731573      6      good
chromium@514641,v8@67d543ec31      0.189568 +- 0.00288097      6      good
chromium@514641,v8@6bb1d47e6e      0.224784 +- 0.00864699      6      bad       <--
chromium@514641,v8@ac0661b358      0.231243 +- 0.00984111      6      bad
chromium@514641,v8@80cb266c75      0.226863 +- 0.00364811      6      bad
chromium@514642                    0.227557 +- 0.00218761      6      bad
chromium@514643                    0.22253 +- 0.00643613       6      bad
chromium@514644                    0.226542 +- 0.0140501       6      bad
chromium@514675                    0.227958 +- 0.0025035       6      bad
chromium@514737                    0.225563 +- 0.01527         6      bad

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 thread_times.tough_compositor_cases

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

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


For feedback, file a bug with component Speed>Bisection