When the bisect identifies a memory regression, it links this doc: https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

The doc doesn't talk about how to get a memory trace though.

The user in https://bugs.chromium.org/p/chromium/issues/detail?id=734619 read the doc and was unable to get a trace or understand exactly what memory:chrome:all_processes:reported_by_chrome:net:effective_size_avg meant after reading.

We do have some documentation on getting traces in this doc that is now linked in perf bugs: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/addressing_performance_regressions.md

Is there a way we could make it easier to get to the traces and grok the docs?