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: https://goto.google.com/crostc-crosperf 7 8The final experiment file should look something like the following (but with 9different actual values for the fields): 10 11``` 12board: lumpy 13remote: 123.45.67.089 14 15# Add images you want to test: 16 17my_image { 18 chromeos_image: /usr/local/chromeos/src/build/images/lumpy/chromiumos_test_image.bin 19} 20 21vanilla_image { 22 chromeos_root: /usr/local/chromeos 23 build: lumpy-release/R35-5672.0.0 24} 25 26# Paste experiment benchmarks here. Example, I pasted 27# `page_cycler_v2.morejs` here. 28 29# This experiment just runs a short autotest which measures the performance 30# of Telemetry's `page_cycler_v2.morejs`. In addition, it profiles cycles. 31 32perf_args: record -e cycles 33 34benchmark: page_cycler_v2.morejs { 35 suite: telemetry_Crosperf 36 iterations: 1 37} 38``` 39 40# default_remotes 41 42This is the list of machines allocated for toolchain team. 43This should be kept in sync with: 44https://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 45