1# experiment_files 2 3To use these experiment files, replace the board, remote and images 4placeholders and run crosperf on them. 5 6Further information about crosperf: 7https://sites.google.com/a/google.com/chromeos-toolchain-team-home2/home/team-tools-and-scripts/crosperf-cros-image-performance-comparison-tool 8 9The final experiment file should look something like the following (but with 10different actual values for the fields): 11 12``` 13board: lumpy 14remote: 123.45.67.089 15 16# Add images you want to test: 17 18my_image { 19 chromeos_image: /usr/local/chromeos/src/build/images/lumpy/chromiumos_test_image.bin 20} 21 22vanilla_image { 23 chromeos_root: /usr/local/chromeos 24 build: lumpy-release/R35-5672.0.0 25} 26 27# Paste experiment benchmarks here. Example, I pasted 28# `page_cycler_v2.morejs` here. 29 30# This experiment just runs a short autotest which measures the performance 31# of Telemetry's `page_cycler_v2.morejs`. In addition, it profiles cycles. 32 33perf_args: record -e cycles 34 35benchmark: page_cycler_v2.morejs { 36 suite: telemetry_Crosperf 37 iterations: 1 38} 39``` 40 41# default_remotes 42 43This is the list of machines allocated for toolchain team. 44This should be kept in sync with: 45https://chromeos-swarming.appspot.com/botlist?c=id&c=task&c=label-board&c=label-pool&c=os&c=status&d=asc&f=label-pool%3Atoolchain&k=label-pool&s=id 46