There are occasionally instances of tasks in the evergreen CI that run out of memory, either via the static link or compile jobs.

The jlink option and limiting the -j are options to deal with this, but it does mean that we are not fully utilizing the system resources.

A system which can determine how much RAM is available and then estimate to a certain degree from files involved or historical data, how much memory it thinks it will need to compile or link, and also employ a 'try, scale back, retry, scale up' feedback loop may provide a general solution.