tree: b4de46c05d5ca82c3c891a51382f918163c27e11 [path history] [tgz]
  1. PRESUBMIT.py
  2. README.md
  3. __init__.py
  4. blink_perf_cmdline/
  5. blink_perf_xml_http_request/
  6. cluster_telemetry/
  7. cros_benchmarks/
  8. heap_profiling/
  9. leak_detection/
  10. memory_extras/
  11. network_service/
  12. oilpan/
  13. oop_raster/
  14. oopd/
  15. orderfile/
  16. tracing/
  17. vr_benchmarks/
tools/perf/contrib/README.md

The code is this directory is neither endorsed nor supported by the Chromium benchmarking team.

To add code in this directory:

  1. First check the list of available benchmarking harnesses at bit.ly/chrome-benchmark-harnesses and make sure that your use case cannot fit any of the supported harness. If there is a related harness, please reach out to us and extend existing functionality.
  2. If your test case cannot fit into any existing harness, create a sub-directory with yourself and at least one another person as the OWNERS. Send the CL containing ONLY the new OWNERS file to the owners of tools/perf/. Your CL description should describe what the code you plan to add do. If it's an ephemeral benchmark used to drive a perf project, you need an accompanied bug (assigned to you) to clean up the benchmarks once your perf project is launched.

NOTE

  1. Benchmarks in this directory will not be scheduled for running on the perf waterfall.
  2. Chromium benchmarking team will NOT review nor maintain any code under this directory. It is the responsiblity of the owners of each sub-directory to maintain them.