Similar documents: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark/harnesses/

I can do this work. Where should I check it in? Where is the repo for it?

Ah nevermind. I see you have a link to it.

Maybe +dougman can do this. Doug, all the information that Ned needs is already documented, but it is in a few places:

A. How to run the tests what the tests are for and lots of links are in go/videostack-sheriff
B. Metrics are documented in https://cs.chromium.org/chromium/src/third_party/catapult/tracing/tracing/metrics/media_metric.html?q=media_metric&g=0&l=1
C. Test cases are listed and documented in https://cs.chromium.org/chromium/src/tools/perf/page_sets/media_cases.py
D. Benchmark code is in https://cs.chromium.org/chromium/src/tools/perf/benchmarks/media.py?type=cs&q=media.desktop&g=0&l=78

After that information is collated into a single document, you make it a markdown file and put
it in chromium/src/docs/speed/benchmark/harnesses/media.md. Reviewers should be crouleau, johnchen,
and nednguyen.

(If Doug can't do this, at least those links are available for me or the next person to do this now :) )

Reducing this to P2 since it isn't blocking any important work that I can tell (If it is, please add that as a blocking bug.)

This actually blocks enabled guidance for Chrome-devs who have to deal with benchmark regressions (https://github.com/catapult-project/catapult/issues/3150#issuecomment-399118294), so I put this back to P1.

We should also add documentation about what to do when benchmark regresses. Example: https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md