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

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


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

android-nexus6
android-webview-nexus6

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

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

Hi chrishtr@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 : Chris Harrelson
  Commit : b13fe9b3f81e3ca635dd79ff606e45b5f2752bbf
  Date   : Wed Jan 10 23:43:34 2018
  Subject: [CI] Clean up PaintLayerClipper data structures

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : smoothness.tough_animation_cases
  Metric       : frame_times/balls_css_transition_2_properties.html
  Change       : 1.07% | 91.8606790763 -> 92.8408680621

Revision             Result                  N
chromium@528400      91.8607 +- 3.54976      14      good
chromium@528452      91.0265 +- 1.48558      6       good
chromium@528478      91.6955 +- 2.07349      9       good
chromium@528482      91.495 +- 1.30944       9       good
chromium@528483      91.6978 +- 2.07894      9       good
chromium@528484      93.5001 +- 2.31223      9       bad       <--
chromium@528485      93.2798 +- 1.80945      6       bad
chromium@528491      92.961 +- 2.61735       9       bad
chromium@528503      93.5394 +- 1.28496      6       bad
chromium@528605      92.8409 +- 3.08323      14      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 --story-filter=balls.css.transition.2.properties.html smoothness.tough_animation_cases

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

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


For feedback, file a bug with component Speed>Bisection

I think the clean up and reduction of memory from subsequent changes (removing
cache lines) justifies any regression here.