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

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


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

android-nexus5X
android-nexus6
android-webview-nexus6

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

=== 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 : Nghia Nguyen
  Commit : 77863be41ffde6f6d149fdd1bf6ce68122288541
  Date   : Wed Jan 03 14:45:34 2018
  Subject: Move the call to set platform performance mode out of platform_backend.DidCreateBrowser and

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : power.typical_10_mobile
  Metric       : application_energy_consumption_mwh/application_energy_consumption_mwh
  Change       : 102.53% | 2.02922958333 -> 4.10978758333

Revision                                 Result                    N
chromium@526720                          2.02923 +- 0.521962       6      good
chromium@526724                          1.69302 +- 0.550189       6      good
chromium@526724,catapult@77863be41f      2.99255 +- 0.74751        6      bad       <--
chromium@526725                          2.80901 +- 0.417242       6      bad
chromium@526726                          3.08159 +- 0.334804       6      bad
chromium@526728                          3.55687 +- 0.10382        6      bad
chromium@526736                          3.60199 +- 0.292171       6      bad
chromium@526752                          3.85161 +- 0.238243       6      bad
chromium@526784                          4.0463 +- 0.175626        6      bad
chromium@526848                          4.10979 +- 0.0805157      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 power.typical_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection

This is just a test change so not a real regression