tree: 554de9a6149ca2fb5672a160d10155fa4dccac1c [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. BUILD.gn
  14. OWNERS
  15. PRESUBMIT.py
  16. README.md
  17. benchmark.csv
  18. bootstrap_deps
  19. convert_legacy_wpr_archive
  20. diagnose_test_failure
  21. expectations.config
  22. export_csv
  23. fetch_benchmark_deps.py
  24. fetch_benchmark_deps_unittest.py
  25. find_dependencies
  26. flakiness_cli
  27. generate_legacy_perf_dashboard_json.py
  28. generate_legacy_perf_dashboard_json_unittest.py
  29. generate_perf_data
  30. generate_perf_sharding
  31. generate_system_health_csv
  32. list_affected_benchmarks
  33. list_benchmarks
  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. update_wpr
  47. validate_perf_json_config
  48. validate_story_expectation_data
  49. 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.