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

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


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

android-nexus5
android-nexus5X
android-nexus7v2
android-webview-nexus5X
android-webview-nexus6
chromium-rel-mac11
chromium-rel-mac11-pro
chromium-rel-mac12-mini-8gb
chromium-rel-win10
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-x64-dual
linux-release

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

=== Auto-CCing suspected CL author nednguyen@google.com ===

Hi nednguyen@google.com, 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 : Ned Nguyen
  Commit : 667e31b9c1e0ecc0ef85aa6c4fe6cce89ff56d42
  Date   : Tue Sep 05 19:54:18 2017
  Subject: Revert "Using speedometer in third_party/webkit/PerformanceTest"

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : speedometer
  Metric       : React-TodoMVC/React-TodoMVC
  Change       : 98.76% | 2077.44388889 -> 4129.10111111

Revision             Result                  N
chromium@499669      2077.44 +- 623.325      6      good
chromium@499695      2064.75 +- 716.421      6      good
chromium@499708      2100.1 +- 694.985       6      good
chromium@499715      2000.52 +- 302.693      6      good
chromium@499717      2142.11 +- 692.608      6      good
chromium@499718      4099.37 +- 1275.01      6      bad       <--
chromium@499721      4137.19 +- 1292.87      6      bad
chromium@499773      4120.23 +- 1206.16      6      bad
chromium@499877      4129.1 +- 1293.85       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/8957599791642695552


For feedback, file a bug with component Speed>Bisection