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