tree: 9c180fc1f144edaa1fa74c2984c64668c97cf142 [path history] [tgz]
  1. .gitignore
  2. BUILD.gn
  3. OWNERS
  4. PRESUBMIT.py
  5. README.md
  6. benchmark.csv
  7. benchmarks/
  8. bootstrap_deps
  9. chrome_telemetry_build/
  10. clear_system_cache/
  11. cli_tools/
  12. contrib/
  13. convert_legacy_wpr_archive
  14. core/
  15. diagnose_test_failure
  16. examples/
  17. expectations.config
  18. experimental/
  19. export_csv
  20. fetch_benchmark_deps.py
  21. fetch_benchmark_deps_unittest.py
  22. find_dependencies
  23. flakiness_cli
  24. generate_legacy_perf_dashboard_json.py
  25. generate_legacy_perf_dashboard_json_unittest.py
  26. generate_perf_data
  27. generate_perf_sharding
  28. generate_system_health_csv
  29. list_affected_benchmarks
  30. list_benchmarks
  31. measurements/
  32. metrics/
  33. page_sets/
  34. pinboard
  35. pinpoint_cli
  36. process_perf_results.py
  37. process_perf_results_unittest.py
  38. pylintrc
  39. record_wpr
  40. run_benchmark
  41. run_telemetry_tests
  42. run_tests
  43. scripts_smoke_unittest.py
  44. soundwave
  45. system_health_stories.csv
  46. testdata/
  47. update_wpr
  48. validate_perf_json_config
  49. validate_story_expectation_data
  50. validate_wpr_archives
tools/perf/README.md

Performance tools

This directory contains a variety of command line tools that can be used to run benchmarks, interact with speed services, and manage performance waterfall configurations.

Note you can also read the higher level Chrome Speed documentation to learn more about the team organization and, in particular, the top level view of How Chrome Measures Performance.

run_benchmark

This command allows running benchmarks defined in the chromium repository, specifically in tools/perf/benchmarks. If you need it, documentation is available on how to run benchmarks locally and how to properly set up your device.

TODO

Documentation for other commands in this directory is also coming.