Hey guys, quick question on max concurrent runs: If no value is set, and only tag_concurrency_limits are applied, how will the Daemon decide how many runs should happen at once to prevent resource starvation?

It won't do anything to prevent resource starvation other than the limits that you set

And I assume that tag_concurrency_limits do not take precedence over max_concurrent_runs right?

It'll enforce both sets of rules, yeah. If you set max_concurrent_runs, there will never be more runs that that at a time, whether or not you set tag concurrency limits

To give some context: I'd love to have two node pools (one for high load pipelines requiring higher capacity machines) and another for small load ones. For the high load ones, I am going to provide more resources so I want to have higher limits, so I assume to do this I will need to get rid of max_concurrent_runs and perhaps have a high_load and low_load tag to handle it

That sounds right to me!