Skip to content

vLLM weight save/load and (mostly) end to end. (Don't merge) - #11

Closed
apaz-cli wants to merge 1 commit into
mainfrom
ap/weight_updates
Closed

vLLM weight save/load and (mostly) end to end. (Don't merge)#11
apaz-cli wants to merge 1 commit into
mainfrom
ap/weight_updates

Conversation

@apaz-cli

Copy link
Copy Markdown
Contributor

No description provided.

@samsja samsja closed this Mar 18, 2025
samsja added a commit that referenced this pull request Nov 11, 2025
* math only and nccl

* add code and seq

* up temp

* 20 ckpt step

---------

Co-authored-by: Mika Senghaas <mail@mikasenghaas.de>
samsja added a commit that referenced this pull request Dec 4, 2025
* math only and nccl

* add code and seq

* up temp

* 20 ckpt step

---------

Co-authored-by: Mika Senghaas <mail@mikasenghaas.de>
snimu added a commit that referenced this pull request May 20, 2026
Updates after read-only inspection of the cluster:

- TTT plan + cheat-sheet now carry the actual cluster facts: H200
  topology, /beegfs storage, vLLM 0.21.0 pin, weight broadcast=nccl,
  Qwen3-4B model cache, production memory pressure (optim_cpu_offload).
- gate_up_proj layerwise fix is already in main (PR #2482); historical
  failure mode noted but no longer needs reproduction. Live SFT-on-tool
  runs validate the SFT path behaviorally — smoke task #1 is implicit.
- New hard invariant from daniel/gptoss-lora-nan-repro HANDOVER: every
  chunk snapshot gets a fresh lora_int_id, never reused. LRU eviction
  handles cleanup. Codified in the cheat-sheet's "things that burned us"
  and as plan invariant #11.
- Multi-LoRA infra is production-hardened via hosted training; TTT risk
  surface narrowed to the chunked-snapshot churn pattern, not the
  multi-LoRA machinery itself.

New files:

- docs/ttt-probes.md: four single-purpose benchmarks the cluster
  session should run before writing Phase A code — snapshot churn,
  learner forward+backward, multi-LoRA forward overhead at
  n_adapters ∈ {1,8,64,256,1024}, /beegfs write throughput. Each has
  pass criteria that gate later phases.
- docs/ttt-config-draft.toml: starter TOML mirroring the production
  Forth qwen-rl.toml shape, with the TTT additions on top. Drops as
  `qwen-rl-ttt.toml` next to qwen-rl.toml in configs/private when
  the cluster session moves it over.
snimu added a commit that referenced this pull request May 22, 2026
Updates after read-only inspection of the cluster:

- TTT plan + cheat-sheet now carry the actual cluster facts: H200
  topology, /beegfs storage, vLLM 0.21.0 pin, weight broadcast=nccl,
  Qwen3-4B model cache, production memory pressure (optim_cpu_offload).
- gate_up_proj layerwise fix is already in main (PR #2482); historical
  failure mode noted but no longer needs reproduction. Live SFT-on-tool
  runs validate the SFT path behaviorally — smoke task #1 is implicit.
- New hard invariant from daniel/gptoss-lora-nan-repro HANDOVER: every
  chunk snapshot gets a fresh lora_int_id, never reused. LRU eviction
  handles cleanup. Codified in the cheat-sheet's "things that burned us"
  and as plan invariant #11.
- Multi-LoRA infra is production-hardened via hosted training; TTT risk
  surface narrowed to the chunked-snapshot churn pattern, not the
  multi-LoRA machinery itself.

New files:

- docs/ttt-probes.md: four single-purpose benchmarks the cluster
  session should run before writing Phase A code — snapshot churn,
  learner forward+backward, multi-LoRA forward overhead at
  n_adapters ∈ {1,8,64,256,1024}, /beegfs write throughput. Each has
  pass criteria that gate later phases.
- docs/ttt-config-draft.toml: starter TOML mirroring the production
  Forth qwen-rl.toml shape, with the TTT additions on top. Drops as
  `qwen-rl-ttt.toml` next to qwen-rl.toml in configs/private when
  the cluster session moves it over.
@mikasenghaas
mikasenghaas deleted the ap/weight_updates branch August 5, 2026 04:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants