tree: 33f6158c540d52b9770661b51cb7296373f44212 [path history] [tgz]
  1. benchmarks/
  2. chrome_telemetry_build/
  3. clear_system_cache/
  4. cli_tools/
  5. contrib/
  6. core/
  7. examples/
  8. measurements/
  9. metrics/
  10. page_sets/
  11. testdata/
  12. .gitignore
  13. benchmark.csv
  14. bootstrap_deps
  15. BUILD.gn
  16. convert_legacy_wpr_archive
  17. diagnose_test_failure
  18. expectations.config
  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. OWNERS
  32. pinpoint_cli
  33. PRESUBMIT.py
  34. process_perf_results.py
  35. process_perf_results_unittest.py
  36. pylintrc
  37. README.md
  38. record_wpr
  39. run_benchmark
  40. run_telemetry_tests
  41. run_tests
  42. scripts_smoke_unittest.py
  43. soundwave
  44. system_health_stories.csv
  45. update_wpr
  46. validate_perf_json_config
  47. validate_story_expectation_data
  48. 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.