Cross Reference: /external/toolchain-utils/crosperf/experiment_files/

To use these experiment files, replace the board, remote and images
placeholders and run crosperf on them.

Further information about crosperf:
https://sites.google.com/a/google.com/chromeos-toolchain-team-home2/home/team-tools-and-scripts/crosperf-cros-image-performance-comparison-tool

The final experiment file should look something like the following (but with
different actual values for the fields):

board: lumpy
remote: 123.45.67.089

# Add images you want to test:
my_image {
  chromeos_image: /usr/local/chromeos/src/build/images/lumpy/chromiumos_test_image.bin
}

vanilla_image {
   chromeos_root: /usr/local/chromeos
   build: lumpy-release/R35-5672.0.0
}

# Paste experiment benchmarks here. Example, I pasted
# page_cycler_v2.morejs here.

# This experiment just runs a short autotest which measures the performance of
# Telemetry's page_cycler_v2.morejs. In addition, it profiles

perg_args: record -e cycles

benchmark: page_cycler_v2.morejs {
   suite: telemetry_Crosperf
   iterations: 1
}
Name	Date	Size
..	10-Aug-2018	4 KiB
aes_perf.exp	10-Aug-2018	690
bloat_perf.exp	10-Aug-2018	789
morejs_perf.exp	10-Aug-2018	793
non-telemetry-tests.exp	10-Aug-2018	846
official-image.exp	10-Aug-2018	1.2 KiB
page_cycler.exp	10-Aug-2018	850
page_cycler_perf.exp	10-Aug-2018	1.1 KiB
README	10-Aug-2018	1,010
telemetry-crosperf-suites.exp	10-Aug-2018	1.8 KiB
telemetry-crosperf-with-external-chrome-src.exp	10-Aug-2018	1.1 KiB
telemetry-crosperf-with-profiler.exp	10-Aug-2018	1.2 KiB
telemetry-crosperf.exp	10-Aug-2018	1.2 KiB
telemetry-without-autotest.exp	10-Aug-2018	1.3 KiB
telemetry_perf_perf	10-Aug-2018	2.4 KiB
trybot-image.exp	10-Aug-2018	1 KiB