tree: 76cce43c5acc430e0b32c6f6a8b2bdb03adb0439 [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. expectations.config
  17. fetch_benchmark_deps.py
  18. fetch_benchmark_deps_unittest.py
  19. find_dependencies
  20. flakiness_cli
  21. generate_legacy_perf_dashboard_json.py
  22. generate_legacy_perf_dashboard_json_unittest.py
  23. generate_perf_data
  24. generate_perf_sharding
  25. generate_system_health_csv
  26. list_affected_benchmarks
  27. list_benchmarks
  28. measurements/
  29. metrics/
  30. page_sets/
  31. process_perf_results.py
  32. process_perf_results_unittest.py
  33. pylintrc
  34. record_wpr
  35. run_benchmark
  36. run_telemetry_tests
  37. run_tests
  38. scripts_smoke_unittest.py
  39. system_health_stories.csv
  40. testdata/
  41. update_wpr
  42. validate_perf_json_config
  43. validate_story_expectation_data
  44. 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.