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

552 CUDA-OOM'd at n_done=45: the user's VS Code GPU kernel grew to 8.18GB
while this fit's 13.23GB hit the 23.5GB ceiling (44MB free, fragmentation).
dim_batch=4 shrinks the fit to ~10.5GB (polite co-tenant, leaves user ~13GB)
and expandable_segments:True defragments (the OOM's own suggestion). Still
only changes the backward schedule, not the Jacobian. Resumes from n_done=45.

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

2026-07-10 14:10:39 +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 8->4 + expandable_segments after 2nd OOM

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