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.
This commit is contained in:
2026-10-26 14:21:24 +01:00
parent ee9fcaba20
commit 9254180cab
4 changed files with 102 additions and 25 deletions
+1 -1
View File
@@ -3,7 +3,7 @@ module github.com/novox/mesh-host
go 1.26.0
require (
git.novox.be/novox/mesh-sdk/go v0.1.14-0.20261026124909-76deab6c67c2
git.novox.be/novox/mesh-sdk/go v0.1.14-0.20261026132005-852ba81c5af1
github.com/nats-io/nats-server/v2 v2.11.17
github.com/nats-io/nats.go v1.54.0
golang.org/x/crypto v0.57.0