Integrate Vortex with official SGLang 0.5.12 plugins#2
Draft
Rockyeast wants to merge 10 commits into
Draft
Conversation
added 10 commits
July 22, 2026 00:37
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
sglang.srt.pluginsentry point for officialsglang==0.5.12.post1ServerArgs, runtime integration, KV-pool sizing and initialization, fused KV writes, and PD receive handlingbatch_size <= 1024contract when SGLang resolves the request-pool capacityMotivation
Vortex previously depended on a repository-local, modified SGLang 0.5.9 checkout and import-time monkey patches. Environments that install official SGLang could parse Vortex configuration without activating the complete sparse-attention runtime, while newer SGLang pool and scheduler interfaces no longer matched the vendored integration.
This change makes Vortex a normal SGLang plugin, keeps the compatibility surface inside
vortex_torch, and fails explicitly when the expected runtime contract is incomplete.Validation
python3 -m unittest discover -v -s tests -p 'test_*.py'(5 passed)python3 -m compileall -q vortex_torch testswith a temporary bytecode cacheinstall_vortex.sh,install_vortex_glm.sh, andexamples/misc/server_launch.shgit diff --checkParameter--vortex-configto successful token generationThe GPU validation is single-node and does not claim multi-node coverage, other GPU architectures, trained-compressor accuracy, or production latency/throughput guarantees.