docs: add validated Jetson Thor DFlash2 serving setup - #164
Open
marcodelpin wants to merge 1 commit into
Open
Conversation
marcodelpin
marked this pull request as ready for review
August 27, 2026 19:51
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
--kv-cache-memory-bytesand--gpu-memory-utilizationinteract in the tested vLLM revisionValidation
The upstream package workflow was reproduced locally on Python 3.12.13:
twine check --strictdflashdflash,dflash generate, anddflash benchmarkThe documented configuration was also checked on a live 128 GB Jetson AGX Thor:
DFlash2Qwen3ForCausalLMdraft model loadedsm_110max_model_len=262144The 256K statement describes allocated KV capacity; it does not claim that a 256K-token prompt was executed.
AI assistance disclosure
This documentation change was AI-assisted and has not yet received independent human code review. The commands, package checks, runtime configuration, and reported capacity were verified against the tested hardware and final diff.