Home | History | Annotate | Download | only in experiment_files 
      1 To use these experiment files, replace the board, remote and images
      2 placeholders and run crosperf on them.
      3 
      4 Further information about crosperf:
      5 https://sites.google.com/a/google.com/chromeos-toolchain-team-home2/home/team-tools-and-scripts/crosperf-cros-image-performance-comparison-tool
      6 
      7 The final experiment file should look something like the following (but with 
      8 different actual values for the fields):
      9 
     10 board: lumpy
     11 remote: 123.45.67.089
     12 
     13 # Add images you want to test:
     14 my_image {
     15   chromeos_image: /usr/local/chromeos/src/build/images/lumpy/chromiumos_test_image.bin
     16 }
     17 
     18 vanilla_image {
     19    chromeos_root: /usr/local/chromeos
     20    build: lumpy-release/R35-5672.0.0
     21 }
     22 
     23 # Paste experiment benchmarks here. Example, I pasted
     24 # page_cycler_v2.morejs here.
     25 
     26 # This experiment just runs a short autotest which measures the performance of
     27 # Telemetry's page_cycler_v2.morejs. In addition, it profiles
     28 
     29 perg_args: record -e cycles
     30 
     31 benchmark: page_cycler_v2.morejs {
     32    suite: telemetry_Crosperf
     33    iterations: 1
     34 }
     35