v0.12.8 – hysteresis for busy detection (router 0.6.8)

Router 0.6.8, agent unchanged (0.16.0). Hysteresis for busy detection.

• What went wrong: a busy node had to keep meeting the entry condition all the time (GPU load above the threshold, 40 %, without a break for sustain_s). A single reading below it started the quiet timer, and after below_for_s the node was free again. A light game at 31–44 % load with 1–2 GiB of foreign VRAM flipped the node between busy and free every 20–60 s (29 times in under an hour). No model was loaded on the node in between, but every free window could have received a request.
• Now: leaving busy is harder than entering it. Once busy, a node stays busy while the GPU load is at or above busy_exit.gpu_util_pct (new, default 20 %, never higher than the node's entry threshold) and foreign VRAM of at least util_requires_foreign_gib is in use. Loading screens below that are covered by below_for_s. When the game ends, its VRAM goes away and the node becomes free after the quiet period as before.
• The end-to-end suite checks that a game with 25 % load and about 1.8 GiB of foreign VRAM keeps the node busy longer than below_for_s.

Deutsch

Router 0.6.8. Hysterese für die Busy-Erkennung: Einmal busy, bleibt ein Knoten busy, solange die GPU-Auslastung über busy_exit.gpu_util_pct (neu, Vorgabe 20 %) liegt und fremdes VRAM belegt ist. Ein leichtes Spiel mit 31–44 % Last schaltete den Knoten vorher alle 20–60 s zwischen busy und free um.