wassnameandClaudypoo ebb912452d U4 step3: dim_batch 16->8 to survive OOM contention with user's VS Code kernel ...

Run 551 was OOM-killed at n_done=36: the user's VS Code Jupyter kernel
(jsteer venv, PID 3214401) co-loaded ~1.5GB VRAM + 1.9GB RAM while the fit
sat at the 22.4/24.6GB ceiling. Clean SIGKILL with no CUDA traceback = host
OOM killer, not a CUDA OOM. dim_batch=8 halves the fit's peak footprint;
it changes only the backward schedule, not the accumulated Jacobian, so U4
exactness is preserved. Resumes from checkpoint (n_done=36), lossless.

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

2026-07-10 13:56:17 +08:00

..

scratch

U4 step3: dim_batch 16->8 to survive OOM contention with user's VS Code kernel

2026-07-10 13:56:17 +08:00

fit_qwen06b.py

fit script: 64-prompt reproducible Qwen3-0.6B Jacobian cache

2026-07-10 13:03:18 +08:00

smoke.py

smoke: fit+steer Qwen3-0.6B on happy/joy end-to-end

2026-07-10 12:51:08 +08:00

u4_step3_fit4b.py

U4 step3: dim_batch 16->8 to survive OOM contention with user's VS Code kernel

2026-07-10 13:56:17 +08:00