7be3fd486c | ||
---|---|---|
.. | ||
README.md | ||
aes_perf.exp | ||
bloat_perf.exp | ||
dut_config.exp | ||
enable_aslr.exp | ||
morejs_perf.exp | ||
non-telemetry-tests.exp | ||
official-image.exp | ||
page_cycler.exp | ||
page_cycler_perf.exp | ||
telemetry-crosperf-suites.exp | ||
telemetry-crosperf-with-external-chrome-src.exp | ||
telemetry-crosperf-with-profiler.exp | ||
telemetry-crosperf.exp | ||
telemetry-without-autotest.exp | ||
telemetry_perf_perf | ||
trybot-image.exp |
README.md
Experiment files
To use these experiment files, replace the board, remote and images placeholders and run crosperf on them.
Further information about crosperf: https://sites.google.com/a/google.com/chromeos-toolchain-team-home2/home/team-tools-and-scripts/crosperf-cros-image-performance-comparison-tool
The final experiment file should look something like the following (but with different actual values for the fields):
board: lumpy
remote: 123.45.67.089
# Add images you want to test:
my_image {
chromeos_image: /usr/local/chromeos/src/build/images/lumpy/chromiumos_test_image.bin
}
vanilla_image {
chromeos_root: /usr/local/chromeos
build: lumpy-release/R35-5672.0.0
}
# Paste experiment benchmarks here. Example, I pasted
# `page_cycler_v2.morejs` here.
# This experiment just runs a short autotest which measures the performance
# of Telemetry's `page_cycler_v2.morejs`. In addition, it profiles cycles.
perf_args: record -e cycles
benchmark: page_cycler_v2.morejs {
suite: telemetry_Crosperf
iterations: 1
}