Having the resource block limiting blocking new bridges based on cpu cores is not always such a good idea. Have a quite powerful server you can have quite low cpu usage when running 4 bridges and the system blocks you from starting new. It would be good to have 2 settings. one for cpu cores and one for utilization. having 30 machines with small amount of data would require minimum 7 cores. We have a lot of small bridges with temp sensors and stuff sending data once every 10min so this does not make sense. However keeping track of the total cpu utilization and blocking new bridges if the instance is heavily loaded is still very good.

you can disable if you know what you are doing. go check out the docs 🙂 the issue is that once you land up in CPU throttling, which is not the same as uilization (a CPU can be struggling and container can be throttled when utilization is at 60%, absolute mindfuck), then umh-core will experience uneexpected behaviour and might not work as expected

yes. it is disabled now, but it would be good to have the option to only disable the core setting and not the utilization watch.