vasilito
b20f45817a
redbear-ci / check (push) Has been cancelled
Real data from a running build: 6 recipes cooking concurrently but only ONE actual compiler process, load 2.2/16. Recipes almost never hit their compile phase simultaneously — most cook-time is single-threaded configure/link/IO — so the strict per_make = jobs/concurrency division starved the one recipe that was compiling (mesa pinned to -j2 while 14 cores idled). Give each concurrent cook the full -j; the active compiler now uses the whole machine and the OS scheduler absorbs the rare overlap. Worst-case parallelism is bounded by cook_jobs * jobs, so build-redbear.sh now defaults COOKBOOK_COOK_JOBS to 4 (was JOBS/2) to cap simultaneous heavy C++ compiles for RAM safety. A shared make jobserver would cap total jobs precisely while keeping full per-recipe -j — noted as the proper long-term fix.