1567135 - Gather FG and BG idle battery results for Chrome v72 on Android

Status: RESOLVED FIXED

(Testing :: Performance, task, P2)

Description

[Alexandru Irimovici]

Run foreground and background idle battery tests against Chromev72 on Android.

The results should be compatible with the info from health dashboards: https://health.graphics/power?browser=geckoview&suite=speedometer&past=month

Comment 1

[Dave Hunt [:davehunt] [he/him] ⌚BST]

When it came to adding the Chrome v72 power results to the health.graphics dashboard, it was discovered that the method for gathering the results differs from the way our Raptor tests gather them. This means we don't have values for cpu/screen/wifi. Could we revisit this and gather some results that could be added to https://health.graphics/power?browser=geckoview&suite=scn-power-idle and https://health.graphics/power?browser=geckoview&suite=scn-power-idle-bg as a fixed point for comparison?

Comment 2

[Marian Raiciof [:marauder]]

Hi Dave,

When i ran the tests for gathering the idle power results i did a sort of a hack job to modify some python files from
https://github.com/mozilla/powerusage-android

At that time, as i remember the power tests from raptor were not landed, I will check again and will run from there.

Comment 3

[Greg Mierzwinski [:sparky]]

:marauder, the code for running the test has been updated to use the same methodology as raptor's power.py file and can be found here: https://github.com/mozilla/powerusage-android/tree/raptor_power

Running the same test as before would require something like the following now, --test-name, and --binary-name are required and the perfherder data is output to the console and stored as a JSON in the output folder: python3 tests/android_pre_post_general_test.py --testtime 5 --test-name testing-chrome --binary-name com.android.chrome --output /home/sparky/Documents/mozwork

Comment 4

[Marian Raiciof [:marauder]]

I finished the measurements and here are the files:
https://drive.google.com/drive/folders/1OoruoDks5MvGOul7j7xniCiy_eC5d0Gg?usp=sharing

Steps to gather the measurements:

• follow the preliminary setup from the readme file:
  https://github.com/mozilla/powerusage-android/tree/raptor_power

• If you need to install all the browsers, please do so. Chrome v72 can be downloaded from:
  https://www.apkmirror.com/apk/google-inc/chrome/chrome-72-0-3626-105-release/google-chrome-fast-secure-72-0-3626-105-android-apk-download/

• $ git checkout raptor_power

• connect the mobile device to your machine using an usb cable

For foreground tests:

• open the required browser and leave it in foreground (i'll use refbrow here), then run the command:
  $ python3 tests/android_pre_post_general_test.py --testtime 5 --test-name "testing-refbrow" --binary-name "org.mozilla.reference.browser" --output ~/Desktop/cpu_memory_battery/fg_refbrow_1

For background tests:

• open the required browser and press home on the mobile screen (i'll use refbrow here), then run the command:
  $ python3 tests/android_pre_post_general_test.py --testtime 5 --test-name "testing-refbrow" --binary-name "org.mozilla.reference.browser" --output ~/Desktop/cpu_memory_battery/bg_refbrow_1

For other browsers we have to change the binaries, test names, and output folder:
--test-name "testing-chrome" --binary-name "com.android.chrome"
--test-name "testing-gve" --binary-name "org.mozilla.geckoview_example"