tree: 36e25644fc26555a888d9e0b3199d7c5fe5a3c8b [path history] [tgz]
  1. README.md
  2. benchmark.py
  3. benchmark_run.py
  4. benchmark_run_unittest.py
  5. benchmark_unittest.py
  6. column_chart.py
  7. compare_machines.py
  8. config.py
  9. config_unittest.py
  10. crosperf
  11. crosperf.py
  12. crosperf_unittest.py
  13. default-telemetry-results.json
  14. default_remotes
  15. download_images.py
  16. download_images_buildid_test.py
  17. download_images_unittest.py
  18. experiment.py
  19. experiment_factory.py
  20. experiment_factory_unittest.py
  21. experiment_file.py
  22. experiment_file_unittest.py
  23. experiment_files/
  24. experiment_runner.py
  25. experiment_runner_unittest.py
  26. experiment_status.py
  27. field.py
  28. flag_test_unittest.py
  29. generate_report.py
  30. generate_report_unittest.py
  31. help.py
  32. image_checksummer.py
  33. label.py
  34. machine_image_manager.py
  35. machine_image_manager_unittest.py
  36. machine_manager.py
  37. machine_manager_unittest.py
  38. mock_instance.py
  39. perf_files/
  40. results_cache.py
  41. results_cache_unittest.py
  42. results_organizer.py
  43. results_organizer_unittest.py
  44. results_report.py
  45. results_report_templates.py
  46. results_report_unittest.py
  47. run_tests.sh
  48. schedv2.py
  49. schedv2_unittest.py
  50. settings.py
  51. settings_factory.py
  52. settings_factory_unittest.py
  53. settings_unittest.py
  54. suite_runner.py
  55. suite_runner_unittest.py
  56. test_cache/
  57. test_flag.py
  58. translate_xbuddy.py
  59. unittest_keyval_file.txt
crosperf/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
}

default_remotes

This is the list of machines allocated for toolchain team. This should be kept in sync with: https://chromeos-swarming.appspot.com/botlist?c=id&c=task&c=label-board&c=label-pool&c=os&c=status&d=asc&f=label-pool%3Atoolchain&k=label-pool&s=id