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

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


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

android-nexus5

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

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

Suspected Commit
  Author : Ashley Enstad
  Commit : 6437bba4ee92ecb4e526c3882eae6338d9d89ed6
  Date   : Wed Aug 16 16:32:45 2017
  Subject: Using speedometer in third_party/webkit/PerformanceTest

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : speedometer
  Metric       : Total/Total
  Change       : 96.72% | 40501.6569444 -> 79676.0269444

Revision             Result                  N
chromium@494796      40501.7 +- 11910.3      6      good
chromium@494807      42801.7 +- 244.181      6      good
chromium@494813      42826.7 +- 410.754      6      good
chromium@494815      40459.4 +- 12539.2      6      good
chromium@494816      79616.6 +- 24205.8      6      bad       <--
chromium@494818      79976.3 +- 22321.3      6      bad
chromium@494840      83864.8 +- 542.673      6      bad
chromium@494883      79676.0 +- 24038.4      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 speedometer

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

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


For feedback, file a bug with component Speed>Bisection