-
Notifications
You must be signed in to change notification settings - Fork 293
[PowerX] enable Kimi-K3 AgentX power backfills / 启用功耗补测 #3030
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
Closed
Closed
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
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
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.
🟡 (optional) The 7 new B200 and 3 new H200 Kimi-K3 AgentX recipes never set ENABLE_AGENTX_POWER/REQUIRE_POWER in benchmark.env, unlike the 13 GB200/GB300 recipes added in the same PR which set both to "1". Without REQUIRE_POWER, benchmark_lib.sh's early _write_agentx_multinode_window check always returns 0 even when the power window/telemetry setup is broken, so a bad setup is only caught by the login-node's post-hoc collect_agentic_power_results after the full ~1h benchmark runs, wasting the GPU job instead of failing in seconds like GB200/GB300 do. Fix: add REQUIRE_POWER: "1" (and ENABLE_AGENTX_POWER: "1") to all 10 B200/H200 recipe env blocks.
Extended reasoning...
run_agentic_replay_and_write_outputs() in benchmarks/benchmark_lib.sh reads REQUIRE_POWER via
case "${REQUIRE_POWER:-0}"before calling _write_agentx_multinode_window; when unset it omits --require-power, so power_adapter.py's run_agentic_power/_fail_multinode_adapter alwaysreturn 1 if require_power else 0i.e. 0. Theif [ "$power_rc" -ne 0 ]; then return "$power_rc"; figuard right after the 'running' window write therefore never trips for B200/H200, letting the full replay run to completion even with broken telemetry. GB200/GB300 recipes set REQUIRE_POWER: "1" so they fail within seconds at the same check. Only the launcher's collect_agentic_power_results (hardcoded --require-power) catches it afterward on B200/H200, after the whole multi-node job already ran.Verification: Severity: nit. The factual/mechanistic claim is real and verified. The 13 GB200/GB300 recipes set ENABLE_AGENTX_POWER="1" and REQUIRE_POWER="1" in benchmark.env (e.g. agg-gb200-tp8pp2-mooncake-c16-agentic.yaml:133-134), but the 7 B200 and 3 H200 recipes add only the telemetry block and concurrencies, no power env keys. On the compute node, agentic_srt.sh:149 calls… | nit. The 10 B200/H200…