page_cycler_perf.exp revision babb65232cbb7de2365d117f3593cdea8a263f05 
1# This experiment profiles some of the Telemetry page cycler tests,
2# uisng 'perf' on the remotes to get performance profiles.
3#
4# You should replace all the placeholders, marked by angle-brackets,
5# with the appropriate actual values.
6
7name: aes_example
8board: <your-board-goes-here>
9
10# Note:  You can specify multiple remotes, to run your tests in parallel on
11# multiple machines. e.g. "remote: test-machine-1.com test-machine2.come
12# test-machine3.com"
13remote: <your-remote-goes-here>
14
15perf_args: record -e cycles,instructions
16
17benchmark: page_cycler_v2.morejs {
18	suite: telemetry_Crosperf
19	iterations: 10
20}
21
22benchmark: page_cycler_v2.bloat {
23	suite: telemetry_Crosperf
24	iterations: 10
25}
26
27benchmark: page_cycler_v2.dhtml {
28	suite: telemetry_Crosperf
29	iterations: 10
30}
31
32benchmark: page_cycler_v2.intl_ar_fa_he {
33	suite: telemetry_Crosperf
34	iterations: 10
35}
36
37benchmark: page_cycler_v2.moz {
38	suite: telemetry_Crosperf
39	iterations: 10
40}
41
42# Replace the chromeos image below with the actual path to your test image.
43test_image {
44  chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin
45}
46