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