tree: 91ec561027cb7c1f4a54c8a56ecefa3468e14d11 [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. list_affected_benchmarks
  30. list_benchmarks
  31. OWNERS
  32. pinboard
  33. pinpoint_cli
  34. PRESUBMIT.py
  35. process_perf_results.py
  36. process_perf_results_unittest.py
  37. pylintrc
  38. README.md
  39. record_wpr
  40. run_benchmark
  41. run_telemetry_tests
  42. run_tests
  43. scripts_smoke_unittest.py
  44. soundwave
  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.

update_wpr

A helper script to automate various tasks related to the update of Web Page Recordings for our benchmarks. In can help creating new recordings from live websites, replay those to make sure they work, upload them to cloud storage, and finally send a CL to review with the new recordings.

pinpoint_cli

A command line interface to the pinpoint service. Allows to create new jobs, check the status of jobs, and fetch their measurements as csv files.

flakiness_cli

A command line interface to the flakiness dashboard.

soundwave

Allows to fetch data from the Chrome Performance Dashboard and stores it locally on a SQLite database for further analysis and processing. It also allows defining studies, pre-sets of measurements a team is interested in tracking, and uploads them to cloud storage to visualize with the help of Data Studio. This currently backs the v8 and health dashboards.

pinboard

Allows scheduling daily pinpoint jobs to compare measurements with/without a patch being applied. This is useful for teams developing a new feature behind a flag, who wants to track the effects on performance as the development of their feature progresses. Processed data for relevant measurements is uploaded to cloud storage, where it can be read by Data Studio. This also backs data displayed on the v8 dashboard.