tree: e0789261c864960926c2149c6a58d52da4c3c50d [path history] [tgz]
  1. aes_perf.exp
  2. bloat_perf.exp
  3. dut_config.exp
  4. enable_aslr.exp
  5. morejs_perf.exp
  6. non-telemetry-tests.exp
  7. official-image.exp
  8. page_cycler.exp
  9. page_cycler_perf.exp
  11. telemetry-crosperf-suites.exp
  12. telemetry-crosperf-with-external-chrome-src.exp
  13. telemetry-crosperf-with-profiler.exp
  14. telemetry-crosperf.exp
  15. telemetry-without-autotest.exp
  16. telemetry_perf_perf
  17. trybot-image.exp

Experiment files

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

Further information about crosperf:

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

board: lumpy

# 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 cycles.

perf_args: record -e cycles

benchmark: page_cycler_v2.morejs {
   suite: telemetry_Crosperf
   iterations: 1