Skip to content

[AMD] MINIMAX-M3 vLLM Agentic Support. - #631

Open
ajith-sirra-amd wants to merge 3 commits into
vllm-project:mainfrom
ajith-sirra-amd:amd_minimax_m3_agentic_support
Open

[AMD] MINIMAX-M3 vLLM Agentic Support. #631
ajith-sirra-amd wants to merge 3 commits into
vllm-project:mainfrom
ajith-sirra-amd:amd_minimax_m3_agentic_support

Conversation

@ajith-sirra-amd

Copy link
Copy Markdown
Contributor

Summary

Adds a KV Cache Offloading guide section to the MiniMax-M3 recipe for AMD MI355X agentic workloads.

Covers two backends (both available on the KV Offload row in the command builder — no per-recipe opt-in needed):

  • Simple (CPU offload)SimpleCPUOffloadConnector, zero extra infrastructure, ~220 GiB host RAM per GPU rank.
  • LMCacheLMCacheMPConnector with a shared CPU-DRAM pool via a companion LMCache server process. ROCm/HIP build path included. Single-node strategies only.

Includes MI355X-specific tuning from the validated InferenceX agentic benchmark:

  • --chunk-size 256 (beats 32 at high concurrency / 1M context)
  • --l1-read-ttl-seconds 7200 (default 300 s TTL too short for TP8/conc32 agentic queues)
  • --max-workers TP × 2, PYTHONHASHSEED=0, LMCACHE_BLOCKING_TIMEOUT_SECS=60

Files changed

…x-M3.yaml File.

Signed-off-by: ajith-sirra-amd <ajith.sirra@amd.com>
@vercel

vercel Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
vllm-recipes Ready Ready Preview, Comment Jul 14, 2026 5:17am

Request Review

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a new 'KV Cache Offloading' section to the MiniMax-M3.yaml guide, detailing Simple CPU offload and LMCache configurations, along with installation steps and tuning notes. The review feedback suggests correcting the lmcache.mp.host parameter by removing the tcp:// prefix to avoid connection failures, and changing the "lazy_offload" value from a string to a boolean literal in the JSON configuration.

Comment thread models/MiniMaxAI/MiniMax-M3.yaml Outdated
Comment thread models/MiniMaxAI/MiniMax-M3.yaml Outdated
…x-M3.yaml File.

Signed-off-by: ajith-sirra-amd <ajith.sirra@amd.com>
@functionstackx

Copy link
Copy Markdown
Contributor

426be25

@ajith-sirra-amd

Copy link
Copy Markdown
Contributor Author

426be25

Already rebased — 426be25 (#628) is our branch base, our commits sit directly on top of it.

@ywang96 ywang96 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's probably better for someone from LMCache side to double check cc @ApostaC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants