wassnameandClaudypoo 57a0276ae6 U4 step3 guard: back off when GPU/RAM in use, yield to the live user ...

Discovered the user is actively developing jsteer (commit 80353ed 90s ago,
live 16GB VRAM kernel from their demo work) -- they are NOT afk. The blind
requeue guard would compete with their interactive work and risk oomd-killing
THEIR process. Now the guard only launches the fit when GPU free >=13GB and
host avail >=20GB, so it fills genuinely-idle windows (overnight) and never
fights the human for their own machine. Killed the competing fit (555) to
yield the GPU now; checkpoint preserved at n_done=69.

Co-Authored-By: Claudypoo <288921227+claudypoo@users.noreply.github.com>

2026-07-10 14:53:35 +08:00

..

scratch

wip

2026-07-10 14:36:55 +08:00

fit.py

demo: chat-template extract+generate, j-space+<think> display (jsteer.demo.show_steer)

2026-07-10 14:48:46 +08:00

smoke.py

add clamp apply mode: pin v-component to C instead of accumulating

2026-07-10 14:42:22 +08:00

u4_step3_fit4b.py

U4 step3: dim_batch 8->4 + expandable_segments after 2nd OOM

2026-07-10 14:10:39 +08:00

u4_step3_guard.sh

U4 step3 guard: back off when GPU/RAM in use, yield to the live user

2026-07-10 14:53:35 +08:00

u4_step3_retry.sh

U4 step3: auto-resume wrapper to self-heal through user's GPU bursts

2026-07-10 14:31:20 +08:00