Add DeepSeek-V4-Flash-Vision-Exp recipe and runtime dependency mod - #382
Closed
isolitude wants to merge 1 commit into
Closed
Add DeepSeek-V4-Flash-Vision-Exp recipe and runtime dependency mod#382isolitude wants to merge 1 commit into
isolitude wants to merge 1 commit into
Conversation
Add the cluster-only deepseek-v4-flash-vision-exp recipe for serving deepseek-ai/DeepSeek-V4-Flash-Vision-Exp (FP8) on a dual DGX Spark cluster with unified vision (index_topk=512, rms_norm_eps=1e-20) plus DSpark speculative decoding. The vision feature comes from local-inference-lab/vllm PR #634 (open, NOT merged into dev/jovian-judgement), so the recipe builds the vllm-node-b12x image with --rebuild-vllm --apply-vllm-pr 634. The #553/#671 functionality is already present in the branch in equivalent form and is not applied. Introduce mods/jj-ds4-vision-deps, the container-start runtime stack for this recipe: - b12x source overlay (pure Python/JIT, no rebuild): PR eugr#301 FP8 dual-cache prefill + sparse topk-512, PR eugr#246 TP2 comm/pcie, PR eugr#306 mHC rms_eps=1e-20 allowance. - LMCache dev+5 build/install from the vendored tarball (dev @7ed46754 + PRs eugr#49/eugr#50/eugr#51/eugr#55/eugr#56, replacing the dropped PR eugr#44). - flashinfer no-op (baked 0.6.18 already carries the SM120 topk-512 dispatch). run.sh is idempotent and self-verifying; verify.sh checks the three claims against the installed environment. Docs added (docs/deepseek-v4-flash-vision-exp.md and a CHANGELOG entry). The mod README documents how to rebuild the vendored LMCache tarball; PR references use full URLs so GitHub links land on the correct upstream repositories, not this one. Co-Authored-By: Claude Code <noreply@anthropic.com>
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
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.
Summary
Add a cluster-only recipe for DeepSeek-V4-Flash-Vision-Exp (FP8) on a dual DGX Spark cluster, with unified vision indexing + DSpark speculative decoding, plus the runtime dependency stack it needs.
What's included
recipes/deepseek-v4-flash-vision-exp.yaml— cluster-only recipe. Builds thevllm-node-b12ximage with--exp-b12x --rebuild-vllm --apply-vllm-pr 634(the vision feature is not merged intodev/jovian-judgement), applies the b12x runtime overlay + LMCache dev+5 install at container start.mods/jj-ds4-vision-deps— the container-start runtime stack:rms_eps=1e-20allowance.lmcache-dev5-src.tar.gz, ~2.2 MB):devbase@7ed46754+ follow-up PRs #49/#50/#51/#55/#56 — this replaces the previously-depended-upon PR #44, which vLLM PR #634 dropped.run.shis idempotent and self-verifying;verify.shchecks the three claims against the installed environment.docs/deepseek-v4-flash-vision-exp.md(dependency stack, PR #634 status, caveats) and a CHANGELOG entry.Dependency stack
rms_norm_eps=1e-20--apply-vllm-pr 634dev/jovian-judgementdev/jovian-judgementdev+ PRs #49/#50/#51/#55/#56 (replaces PR #44)803c4664SM120 sparse-MLA topk-512Why LMCache dev + follow-up PRs, not PR #44?
PR #634's runtime-dependency list dropped PR #44 (the
release/v0.5.2-glm52-dcp-baselineage) in favor of five dev-lineage PRs #49/#50/#51/#55/#56. The dev engine-driven path is a different implementation from #44's (noEngineDrivenContextPickle; the context lives inworker_transfer.pyasEngineDrivenTransferContext). Build the dev+5 source, not #44 or anyrelease/v0.5.xwheel.Notes
--hf-overrides '{"architectures":["DeepseekV4ForConditionalGeneration"]}'is required (the model loader resolves from rawhf_config.architectures).