-
Notifications
You must be signed in to change notification settings - Fork 217
[WIP] Test Kimi 2.5 B300 Agg #1998
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
wzhao18
wants to merge
2
commits into
main
Choose a base branch
from
wzhao/kimi-agentx-b300
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+103
−27
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 The three variables
MOONCAKE_EVICTION_HIGH_WATERMARK_RATIO=0.80,MOONCAKE_EVICTION_RATIO=0.10, andMOONCAKE_KV_LEASE_TTL=60s(lines 97-99) are assigned but never referenced by themooncake_masterinvocation, which instead hardcodes--default_kv_lease_ttl=1h— directly contradicting the declared60s— and omits the two eviction flags entirely, so upstream defaults (~0.95/0.05) apply. Every sister Mooncake recipe (dsv4_fp4_b200_vllm.sh,dsv4_fp4_b300_vllm.sh,minimaxm3_fp8_*) plumbs all three variables through with--eviction_high_watermark_ratio,--eviction_ratio, and--default_kv_lease_ttl. Either wire the vars in (and pick one lease TTL) or delete the dead assignments.Extended reasoning...
What the bug is. In the new Mooncake branch of
kimik2.5_fp4_b300.sh, three env-style vars are declared at lines 97-99 and never referenced again:Three lines later, the master is launched with a hardcoded lease TTL and no eviction flags:
Two concrete defects.
--default_kv_lease_ttl=1hcontradictsMOONCAKE_KV_LEASE_TTL=60s. One of these values must be wrong — both cannot represent the author's intent. Since the declared variable is dead, whichever value was tuned first was lost during editing.--eviction_high_watermark_ratioand--eviction_ratio, the master falls back to upstream defaults (roughly 0.95 / 0.05), not the 0.80 / 0.10 the vars declare.Cross-recipe comparison. Every other agentic Mooncake recipe in this repo declares the same three variables and wires them through:
benchmarks/single_node/agentic/dsv4_fp4_b200_vllm.sh:139-141— passes all three:--eviction_high_watermark_ratio="$MOONCAKE_EVICTION_HIGH_WATERMARK_RATIO" --eviction_ratio="$MOONCAKE_EVICTION_RATIO" --default_kv_lease_ttl="$MOONCAKE_KV_LEASE_TTL".benchmarks/single_node/agentic/dsv4_fp4_b300_vllm.sh:136-142— same pattern, with a comment stating the eviction tuning exists to "start eviction before an imbalanced rank exhausts its segment, and reclaim enough space for several concurrent multi-GB batch puts".benchmarks/single_node/agentic/minimaxm3_fp8_h100.sh:66-68(and the h200/mi300x/mi325x siblings) — all wire both eviction flags.Step-by-step proof.
{ tp: 4, ep: 1, kv-offloading: dram, kv-offload-backend: mooncake, conc-list: [64, 72, 80] }toconfigs/nvidia-master.yaml.mooncake)branch (line 61+).benchmark_lib.sh) references them — grep confirms zero uses.--default_kv_lease_ttl=1hand nothing else. So the actual runtime state is: watermark ≈ 0.95, evict-ratio ≈ 0.05, lease = 1h. Declared intent (0.80 / 0.10 / 60s) never takes effect.Impact. The sweep will still run — Mooncake defaults are functional. But the tuned eviction knobs exist in sister recipes for a documented reason (imbalanced-rank segment exhaustion under concurrent multi-GB puts), and this sweep hits the same regime: TP=4, CONC 64/72/80 with DRAM offload. Without
--eviction_high_watermark_ratioand--eviction_ratio, if a single rank drifts hot it can OOM its segment before eviction begins. Additionally, the 60s-vs-1h contradiction leaves a live ambiguity — a future reader looking atMOONCAKE_KV_LEASE_TTL=60swill reasonably assume 60s is in effect and act on that belief.Fix. Either plumb the variables through, matching the sister B300 recipe:
…or delete the three unused assignments and accept
1h/ defaults as the intended configuration.