1*760c253cSXin Li# experiment_files 2*760c253cSXin Li 3*760c253cSXin LiTo use these experiment files, replace the board, remote and images 4*760c253cSXin Liplaceholders and run crosperf on them. 5*760c253cSXin Li 6*760c253cSXin LiFurther information about crosperf: https://goto.google.com/crostc-crosperf 7*760c253cSXin Li 8*760c253cSXin LiThe final experiment file should look something like the following (but with 9*760c253cSXin Lidifferent actual values for the fields): 10*760c253cSXin Li 11*760c253cSXin Li``` 12*760c253cSXin Liboard: lumpy 13*760c253cSXin Liremote: 123.45.67.089 14*760c253cSXin Li 15*760c253cSXin Li# Add images you want to test: 16*760c253cSXin Li 17*760c253cSXin Limy_image { 18*760c253cSXin Li chromeos_image: /usr/local/chromeos/src/build/images/lumpy/chromiumos_test_image.bin 19*760c253cSXin Li} 20*760c253cSXin Li 21*760c253cSXin Livanilla_image { 22*760c253cSXin Li chromeos_root: /usr/local/chromeos 23*760c253cSXin Li build: lumpy-release/R35-5672.0.0 24*760c253cSXin Li} 25*760c253cSXin Li 26*760c253cSXin Li# Paste experiment benchmarks here. Example, I pasted 27*760c253cSXin Li# `page_cycler_v2.morejs` here. 28*760c253cSXin Li 29*760c253cSXin Li# This experiment just runs a short autotest which measures the performance 30*760c253cSXin Li# of Telemetry's `page_cycler_v2.morejs`. In addition, it profiles cycles. 31*760c253cSXin Li 32*760c253cSXin Liperf_args: record -e cycles 33*760c253cSXin Li 34*760c253cSXin Libenchmark: page_cycler_v2.morejs { 35*760c253cSXin Li suite: telemetry_Crosperf 36*760c253cSXin Li iterations: 1 37*760c253cSXin Li} 38*760c253cSXin Li``` 39*760c253cSXin Li 40*760c253cSXin Li# default_remotes 41*760c253cSXin Li 42*760c253cSXin LiThis is the list of machines allocated for toolchain team. 43*760c253cSXin LiThis should be kept in sync with: 44*760c253cSXin Lihttps://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