chore(scripts): vast.ai sync + debug toolkit from the M11 offload audit - #41
Open
zhenyulincs wants to merge 1 commit into
Open
chore(scripts): vast.ai sync + debug toolkit from the M11 offload audit#41zhenyulincs wants to merge 1 commit into
zhenyulincs wants to merge 1 commit into
Conversation
Track the vast-compute tooling used throughout the offload audit and
smoke sessions (force-added past the scripts/ ignore, same as the
already-tracked run_smoke_*.sh):
- sync_to_vast.sh rsync rlix + miles working trees to an instance
(env-overridable paths/key), push tooling to /root,
optional --setup one-shot env bootstrap
- vast_setup.sh instance setup per docs/smoke-test-runbook.md
(deps, model, datasets, torch_dist ckpt, patches)
- vast_debug_run.sh on-instance debug runner (single|dual driver)
- debug_pipeline.py editable/IDE-debuggable pipeline launcher
- apply_sglang_patches.py runbook Step 8 SGLang compat patches,
idempotent
- audit_gpu_sampler.sh 1 Hz whole-GPU + per-process memory sampler
- run_smoke_audit.sh single-pipeline low-host-RAM audit smoke
- mock_offload_test.py / mock_sglang_offload_test.py /
test_offload_simple.py standalone tms/engine offload repros
No library code changes; scripts only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Tracks the vast-compute tooling built and used during the M11 offload audit and smoke sessions — until now these lived only in my local working tree (
scripts/is gitignored; force-added following the precedent of the already-trackedrun_smoke_*.sh).sync_to_vast.sh/root/rlix,/root/miles) and push the tooling below to/root/;--deletefor exact mirror,--setupto kick off the one-shot env bootstrap,--dry-runsupported. Paths/SSH key are env-overridable.vast_setup.shdocs/smoke-test-runbook.md: deps, model download, datasets, torch_dist checkpoint conversion, SGLang patches. Logs to/root/setup.log, ends withSETUP_DONEmarker.vast_debug_run.shdebug_pipeline.pyapply_sglang_patches.pyaudit_gpu_sampler.shmemory.used+ per-compute-process attribution, one block per second.run_smoke_audit.shmock_offload_test.py/mock_sglang_offload_test.py/test_offload_simple.pyWhy track them
These are the reproduction path for every audit finding referenced in #17 / #31 and the smoke-test-runbook — keeping them local means nobody else can rerun the audit.
sync_to_vast.sh's own tooling list is the canonical set (it ships 8 of these to/root/on every sync).Notes
.gitignoreuntouched (scripts/stays ignored for personal scratch; tracked files are unaffected).