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

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


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

android-nexus7v2

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

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

Hi ksakamoto@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 : Kunihiko Sakamoto
  Commit : 6c41874caefd3b6aabc2cb6645b833c60bc5e8bf
  Date   : Mon Jun 26 03:23:00 2017
  Subject: Revert "Remove usage of FILE thread from devtools_http_handler"

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : blink_perf.paint
  Metric       : LocalFrameView::prePaint/LocalFrameView::prePaint
  Change       : 1.86% | 356.910857143 -> 363.549011905

Revision             Result                  N
chromium@482179      356.911 +- 2.26777      6      good
chromium@482187      354.277 +- 3.69494      6      good
chromium@482189      357.259 +- 2.8178       6      good
chromium@482190      363.249 +- 4.20464      6      bad       <--
chromium@482191      363.426 +- 6.44723      6      bad
chromium@482194      366.457 +- 3.20619      5      bad
chromium@482208      363.549 +- 3.56413      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 blink_perf.paint

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

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


For feedback, file a bug with component Speed>Bisection

r482190 is just a revert of r482066. I don't think this is the cause of the regression.

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

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

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

Hi suzyh@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 : suzyh
  Commit : da913699c72d5f97405db96ddaa4040ed621a0bc
  Date   : Mon Jun 26 03:00:44 2017
  Subject: Expose getAnimations as function on Document

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : blink_perf.paint
  Metric       : LocalFrameView::prePaint/LocalFrameView::prePaint
  Change       : 2.05% | 355.671970899 -> 362.962335979

Revision             Result                  N
chromium@482179      355.672 +- 2.5342       6      good
chromium@482187      353.931 +- 1.78296      6      good
chromium@482188      360.804 +- 3.86167      6      bad       <--
chromium@482189      358.952 +- 1.78347      6      bad
chromium@482191      363.68 +- 4.12548       6      bad
chromium@482194      366.091 +- 7.2934       6      bad
chromium@482208      362.962 +- 5.05796      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 blink_perf.paint

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

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


For feedback, file a bug with component Speed>Bisection

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

Suspected Commit
  Author : Xianzhu Wang
  Commit : 94e1d1e92fa1d4734de08210747d36126ce235aa
  Date   : Sun Jun 25 21:49:01 2017
  Subject: Paint all collapsed borders of a row (or table) as one display item

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : blink_perf.paint
  Metric       : LocalFrameView::prePaint/LocalFrameView::prePaint
  Change       : 7.74% | 337.962667989 -> 364.108854497

Revision             Result                  N
chromium@482171      337.963 +- 2.88441      6      good
chromium@482174      337.282 +- 1.07587      6      good
chromium@482175      337.607 +- 1.73497      6      good
chromium@482176      355.711 +- 1.18938      6      bad       <--
chromium@482181      355.977 +- 1.60617      6      bad
chromium@482190      361.046 +- 2.52563      6      bad
chromium@482208      364.109 +- 4.9513       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 blink_perf.paint

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

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


For feedback, file a bug with component Speed>Bisection