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

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

perf_args: record -e cycles

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