Background context:go/memory-infra: memory profiling in chrome://tracing

From internal thread: "Re: Current status of bisect on internal clank waterfall"
(Keeping track of this on a more persistent medium. My inbox has proven to be more volatile than organic compounds.)

Temporarily assigning to picksi@ to reduce the chances that we forget about this. picksi@ no direct action is expected on your side, other than reminding us about this :)

from primiano@:
-------
I think once this fire is over we should sit down and write down a "how to debug a memory alert" wiki page to explain all these strategies.
Still feels bad to me that we have lot of data and we are not properly using it (and to be clear I think this on us, memory-infra. Usual lack of bandwidth / new problems jumping in our queues every week).
I hope after the TBMv2 transition + new benchmarks we'll be able to sit down and figure out how to squeeze the most info out of this data. :)
In the meantime a wiki page that explains how to do some basic analysis to humans might help the situation.
-------

from sullivan@
-------
Thanks, Primiano! I think having a clear doc everyone can read on how we manually drill down will make it easier for speed infra team to support a better TBM2-based UI in the long term.
-------