Did you want to move it to the chromium.perf.fyi waterfall as well? (Right now it's on chromium.android.fyi)

Yes, we want to move it.
Maybe call it "Memory Infra Perf FYI" then?

I would avoid putting FYI in the bot name.

Ok, "Memory Infra Perf" sgtm

Ok, I can get to this sometime next week. (If you'd rather it be done before then, you're more than welcome to take a stab at it yourself.)

Fix comment 5
"Android Memory Infra Perf" I meant

Friendly ping on this :)

Just looked into it. I forgot how special-case perf's recipe & testing configs are. Given that this bot has specific compiler flags, is a builder-tester, and runs swarming tests that don't have device-affinity, this seems like it's going to require some novel support to both of those
https://cs.chromium.org/chromium/build/scripts/slave/recipe_modules/chromium_tests/chromium_perf_fyi.py
and
https://cs.chromium.org/chromium/src/tools/perf/core/perf_data_generator.py

Moving this over to the perf queue.

I have a clarifying question given I am late to this game. 

Why are we adding new linux and android bots instead of adding these performance tests to the existing configurations?  Given our overhaul of the configurations on the chromium.perf master I would like to understand the need for new hardware. 

Ok is it appropriate to run contrib benchmarks on non-FYI waterfall?
We can't promise a support level expected for normal benchmarks (sheriffing, etc.)

eyaich@: for benchmarks that perf team are not willing to provide support & sheriffing, we let them run it on perf FYI.

kraynov@: you can migrate your heap_profiling.mobile.* benchmarks to perf FYI now.

The way to do this:

1) Add your benchmarks to https://cs.chromium.org/chromium/src/tools/perf/chromium.perf.fyi.extras.json (see example in "Android Nexus 5X Perf FYI")
2) run: tools/perf/generate_perf_data
3) Upload CL

Resolved different way in https://crbug.com/786385