(keeping some notes of a discussion I had with iannucci@)

The number of concurrent links we want to run in a build is set statically[1] (based on the machine specs, or with a fixed limit[2] on the official bots).

This is something that could break easily if the linker memory usage increases.

One way to do this would be to track the memory usage when doing a link and save it with git notes (e.g. in the "/refs/notes/telemetry/link_memory_usage/<platform>" branch). This way we'll be able to have a dynamic linker controller.

The linker memory usage is directly influenced by the GN flags (e.g. the optimization level etc), so it's something that we'll have to track as well.


[1] https://cs.chromium.org/chromium/src/build/toolchain/get_concurrent_links.py?type=cs&q=get_concurrent_links+package:%5Echromium$&l=1

[2] https://cs.chromium.org/chromium/src/tools/mb/mb_config.pyl?l=1831&rcl=222a3fe7a738486a887bb53cffb8e3b52376f609