1 # This example experiment file shows how to invoke the profiler (via 2 # the perf_args above the benchmark). 3 # 4 # You should replace all the placeholders, marked by angle-brackets, 5 # with the appropriate actual values. 6 7 8 name: telemetry_crosperf_profiler_example 9 10 board: <your-board-goes-here> 11 12 # Note: You can specify multiple remotes, to run your tests in parallel on 13 # multiple machines. e.g. "remote: test-machine-1.com test-machine2.come 14 # test-machine3.com" 15 remote: <your-remote-goes-here> 16 17 # Below is the line that causes the profiler to run. Currently the 18 # only profiler option is running 'perf' on the remote machine. If 19 # you want you can replace 'record' with 'stat'. You would also need 20 # to change the other args accordingly. Crosperf automatically 21 # inserts a '-a' if you use 'record' for you perf_args. The results 22 # of the perf run (perf.data and perf.report files) will be available 23 # with the rest of the Crosperf results. 24 perf_args: record -e cycles,instructions 25 26 benchmark: page_cycler_v2.dhtml { 27 suite: telemetry_Crosperf 28 iterations: 1 29 } 30 31 # Replace the chromeos image below with the actual path to your test imnage. 32 test_image { 33 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin 34 } 35 36
