Build seats yield: the decoder, buildcpu and NodeLimits (issue 1806, ADR 0553/0554, change A) #94

Merged

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

Conversation 3 Commits 6 Files Changed 9

+424 -4

6 Commits

Author	SHA1	Message	Date
jschoubben	17b7cc480d	Merge main into fix/build-cpu-yields	2026-10-26 14:46:01 +01:00
jschoubben	527d87613e	Without the composer's share a step has no thread limit; with it, the share over the module's own capacity (ADR 0553 round 2) ... Review round 2: change A must not slow builds before any slice exists, so a module given no share sets no GOMAXPROCS. The slice's quota bounds the total; threads only size one step, from the node's share over the module's own capacity (shanks: 24 x 50% / 3 = 4). The share is the node-engine's own config.	2026-10-26 14:39:39 +01:00
jschoubben	36c92861d2	Merge main into fix/build-cpu-yields	2026-10-26 14:22:26 +01:00
jschoubben	852ba81c5a	Build seats yield to one shared slice per node; the composer half waits for the engines (ADR 0553, issue 1806) ... Review round 1: the decoder type ships before any composer can emit it, so a routine SDK bump never sends yields to an engine that refuses them; the composer half moves to a later change. Every yielding process of a node goes into one top-level slice, meshyield.slice, so the three build modules share one quota instead of taking one each; the share is one node value, node-tools' build-cpu-share, and each step's threads divide it by every build slot of the node (words from the composer, a conservative fallback without them).	2026-10-26 14:20:05 +01:00
jschoubben	76deab6c67	gofmt the cap's test (issue 1806)	2026-10-26 13:49:09 +01:00
jschoubben	04902ff24a	Build seats yield: idle priority and a per-node processor cap on their runtimes, threads per step within it (issue 1806) ... The operator's desktop slows while it builds: the Go build runtime took 1650% of shanks' 24 processors with nothing holding it back. A build seat's holder now runs its runtime at idle priority under its node's cpu-cap share (declaration Yields, composed from Seat.Yields and the module's cpu-cap setting), and buildcpu/buildstep give each step its part of that cap in threads.	2026-10-26 13:37:00 +01:00