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

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


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

android-nexus7v2

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_GPU_cpu_time_per_frame/http___cuteoverload.com

Revision             Result                   N
chromium@490675      3.13792 +- 0.565069      21      good
chromium@490681      3.08108 +- 0.568929      21      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=http...cuteoverload.com thread_times.key_mobile_sites_smooth

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Hi mtklein@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 : Mike Klein
  Commit : 5f9b59b52db2b9a11d41bb7fa93ec5e5d6104236
  Date   : Sat Jul 29 12:28:32 2017
  Subject: use new Stage ABI for ARMv7 too

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_GPU_cpu_time_per_frame/http___cuteoverload.com
  Change       : 13.01% | 2.78504878178 -> 3.1474584063

Revision                             Result                    N
chromium@490000                      2.78505 +- 0.0634163      6      good
chromium@490400                      2.75571 +- 0.16949        6      good
chromium@490600                      2.65596 +- 0.122717       6      good
chromium@490650                      2.70128 +- 0.173267       6      good
chromium@490657                      2.71999 +- 0.0699287      6      good
chromium@490660                      2.68031 +- 0.0685749      6      good
chromium@490660,skia@5f9b59b52d      3.00646 +- 0.43156        6      bad       <--
chromium@490661                      3.16025 +- 0.0887005      6      bad
chromium@490662                      3.15595 +- 0.135087       6      bad
chromium@490663                      3.0673 +- 0.231734        6      bad
chromium@490675                      3.1174 +- 0.124306        6      bad
chromium@490700                      3.05616 +- 0.0816902      6      bad
chromium@490800                      3.14746 +- 0.264994       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 --story-filter=http...cuteoverload.com thread_times.key_mobile_sites_smooth

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

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


For feedback, file a bug with component Speed>Bisection

"use new Stage ABI for ARMv7 too" is a mixed bag of wins and losses, but we think the wins are winning.  Going to WontFix this for now.