The node-engine runs yielding processes in one capped idle slice (issue 1806, ADR 0553/0554, change A) #148

Merged

mesh-tools merged 7 commits from fix/build-cpu-yields into main 2026-10-26 14:22:55 +00:00

Conversation 2 Commits 7 Files Changed 5

+150 -15

7 Commits

Author	SHA1	Message	Date
jschoubben	a78239b2aa	Pin mesh-sdk at fix/build-cpu-yields' head (ADR 0553, ADR 0554)	2026-10-26 14:47:02 +01:00
jschoubben	2ac0c4686a	The node-engine holds the node's one build CPU share as its own config (ADR 0553 §3, round 2) ... The share belongs to the part that enforces it: build-cpu-share, default 50, set per node through the node's settings layer and read by the composer for the build seats' runtimes. Pin mesh-sdk at fix/build-cpu-yields' head.	2026-10-26 14:40:24 +01:00
jschoubben	5233f7584d	Pin mesh-sdk at fix/build-cpu-yields' head (ADR 0553)	2026-10-26 14:23:13 +01:00
jschoubben	8858dba25e	Merge main into fix/build-cpu-yields	2026-10-26 14:22:43 +01:00
jschoubben	9254180cab	A yielding process runs in the node's one yielding slice, which holds the shared quota (ADR 0553, issue 1806) ... Review round 1: one quota per unit let three build modules take three shares. The engine now writes meshyield.slice, top-level so its idle weight binds against the operator's session, with the node's share as its CPUQuota; each yielding unit joins it at nice 19. Comments say the IO controls bind only under bfq or io.cost, not under the none scheduler NVMe disks use.	2026-10-26 14:21:24 +01:00
jschoubben	ee9fcaba20	Pin mesh-sdk at fix/build-cpu-yields' head (issue 1806)	2026-10-26 13:49:41 +01:00
jschoubben	6250b1274b	A process that yields is written at idle priority under its share of the machine (issue 1806) ... A build seat's runtime took 1650% of shanks' 24 processors and slowed the operator's desktop. The unit of a process declared with yields now carries CPUWeight=idle, IOWeight=1, Nice=19, the lowest best-effort IO level, and CPUQuota for its share of the processors this machine has.	2026-10-26 13:37:48 +01:00