1# This experiment template shows how to run Telemetry tests (using autotest) 2# with explicitly specified DUT configurations. 3# 4# You should replace all the placeholders, marked by angle-brackets, 5# with the appropriate actual values. 6 7name: dut_config_telemetry_crosperf_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 15# DUT configuration parameters. All are optional. 16# 17# Run turbostat process in background. Default: True. 18turbostat: <True|False> 19# Run top process in background with specified interval of sampling in 20# seconds, type float. 0 - don't run top. 21# Default: 0 22# Recommended values 1-5 (Lower number provides more accurate data). 23# NOTE: Running top with interval 1-5 sec has insignificant 24# performance impact (performance degradation does not exceed 0.3%). 25top_interval: <interval_in_seconds_float> 26# One of Intel Pstate modes defined in kernel command line: 27# active, passive, no_hwp. 28intel_pstate: <active|passive|no_hwp> 29# Wait until CPU cools down to a specified temperature 30# in Celsius or cooldown_time timeout reaches zero 31# (whichever happens first). Default: 40. 32cooldown_temp: <temperature-threshold-for-cooldown> 33# Timeout specified in minutes for CPU cooling down 34# to cooldown_temp temperature. Zero value disables cooldown. 35# Default: 0. 36cooldown_time: <time-to-cooldown-in-minutes> 37# CPU governor. 38# See: https://www.kernel.org/doc/Documentation/cpu-freq/governors.txt 39# for available values (they might differ for ARM and Intel). 40governor: <one-of-scaling_available_governors-values> 41# Restrict CPU usage to predefined "models": 42# all, big_only, little_only, exclusive_cores. 43cpu_usage: <usage-model> 44# Setup CPU frequency as percent of max_freq. 45# Default: 100 46cpu_freq_pct: <0-100> 47 48# The example below will run Telemetry toolchain performance benchmarks. 49# The exact list of benchmarks that will be run can be seen in 50# crosperf/experiment_factory.py 51benchmark: all_toolchain_perf { 52 suite: telemetry_Crosperf 53 run_local: False 54 iterations: 1 55} 56 57# NOTE: You must specify at least one image; you may specify more than one. 58# Replace <path-to-your-chroot-goes-here> and <board-goes-here> below. 59vanilla_image { 60 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/vanilla-image/chromiumos_test_image.bin 61} 62 63# Replace the chromeos image below with the actual path to your test image. 64test_image { 65 chromeos_image:<path-to-your-chroot>/src/build/images/<board>/test-image/chromiumos_test_image.bin 66} 67