Kimi-K3 FP8 MI355X vLLM agentic recipe (base + DSpark MTP) - #2585
Draft
xiaohuguo2023 wants to merge 1 commit into
Draft
Kimi-K3 FP8 MI355X vLLM agentic recipe (base + DSpark MTP)#2585xiaohuguo2023 wants to merge 1 commit into
xiaohuguo2023 wants to merge 1 commit into
Conversation
Signed-off-by: Xiaohu Guo <Xiaohu.Guo@amd.com>
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.
Description
ROCm/MI355X (gfx950, TP8) recipe for the Kimi-K3 agentic trace-replay
benchmark via vLLM + AITER — the AMD counterpart to
benchmarks/single_node/agentic/kimik3_fp4_b300_vllm*.sh. Same AIPerf cc-tracesharness and dataset as the B300 baseline, so the MI355X points drop onto the same
Pareto apples-to-apples.
Two recipes (
benchmarks/single_node/agentic/):kimik3_fp4_mi355x_vllm.sh— base (non-spec).kimik3_fp4_mi355x_vllm_mtp.sh— DSpark speculative decoding (K=2, syntheticgolden AL 2.51); the arm comparable to
kimik3_fp4_b300_vllm_mtp.sh.Precision. Mixed AITER path — MoE experts A8W4 (
AITER_SITUV2_A8W4, 4-bitweights / 8-bit activations), dense MLA attention in fp8 ASM (
ROCM_AITER_MLAasm-persistent), fp8 KV cache. Not a uniform NVFP4 checkpoint. Recipe filenames
keep the
fp4_*stem for parity with the B300 sibling; the branch/title say FP8 toreflect the dominant activation/attention path. (Happy to make these consistent
either way — see open question below.)
Reproduce-from-base-image. No prebuilt image and no copy of the NV waiver
layout. The image pinned in
configs/amd-master.yamlis the stock ROCm vLLMnightly (
cb8104839c...);apply_k3_container_patches.shidempotently patches itin-container at startup:
metadata, fp8-PS skip, wvsplitk;
No-op once markers are present;
SKIP_K3_BOOTSTRAP=1for a pre-baked image.Mandated serving config (unchanged from the validated sweep): gpu-mem 0.95,
max-num-seqs 64, MNBT 16384,
FULL_AND_PIECEWISEcudagraphs with{12,36}capturesizes (lands conc-4/12 DSpark decode on FULL graphs, removing the
get_mla_metadata_v1host bubble),ROCM_AITER_MLAasm padding, KV-offload vianative/vllm-simplebackends.Config.
configs/amd-master.yamladdskimik3-fp4-mi355x-vllm-agentic(base)and
kimik3-fp4-mi355x-vllm-agentic-dspark(spec-decoding: mtp) blocks; bothvalidate via
generate_sweep_configs test-config.