feat: add Mooncake GPU-direct capture materialization - #775
Draft
Boreas618 wants to merge 10 commits into
Draft
Conversation
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
Companion SGLang draft: sgl-project/sglang#35577
Hardware benchmark
Run on 2026-08-21 UTC. The fixed target was SGLang
60e519391d59on 8x NVIDIA H200 (driver 580.105.08), split into two TP4 Qwen3.8-27B-FP8 replicas. A second H200 host ran the consumer on one GPU. Capture used Mooncake RDMA, DSpark taps[5, 19, 33, 47, 61], and a 32 GiB target arena per replica.The repository base does not contain the GPU-direct FeatureStore, so the same protocol cannot run there. The baseline is the PR's first functional implementation (
1f5a05bfb8b0) and the post-change checkout is PR head (9ce0b698c98c). The baseline used the PR's first live RDMA benchmark harness with only its later-onlyproducer_ordered_publishkeyword removed; production code was unchanged. Each value is the median of two completed 512-sample runs withmax_length=8192, concurrency 64, and ingest batch 128.CLI-equivalent controlled comparison
Both checkouts used lease 1, prefetch 0, shared replica routing, shuffled prompts, and serial materialization.
The baseline harness does not emit a pipeline metric, so its serial pipeline value is conservatively derived as
512 / (capture_elapsed + materialize_elapsed). The PR-head value uses the harness's measured pipeline interval.Tuned PR-head path
The tuned path enabled lease 8, prompt prefetch 4, least-tokens replica routing, length-bucketed requests, batch cleanup, and overlapped capture/materialization.
Every completed run produced and removed all 512 samples, transferred 40,503,867,376 bytes, and reported zero host payload bytes. After each tuned run, both SGLang control endpoints reported no resident or reserved samples,
published_samples == released_samples, and the full 32 GiB arena free.The 1024-sample stress case was excluded from throughput statistics because the harness intentionally retains every sample until the final durable acknowledgement; its retained set exceeds the aggregate 64 GiB target capacity.
Builds, unit tests, integration tests, and CI were not run as part of this hardware benchmark.