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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.mobile_infinite_scroll_tbmv2
  Metric       : v8-gc-scavenger_avg/pinterest

Revision             Result                  N
chromium@483461      2.84293 +- 2.65839      21      good
chromium@483576      2.99889 +- 3.19163      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=pinterest v8.mobile_infinite_scroll_tbmv2

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

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


For feedback, file a bug with component Speed>Bisection

Just returning to previous levels for a bimodal test