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