-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Quantization and MoE configs for GH200 machines #12717
Conversation
👋 Hi! Thank you for contributing to the vLLM project. Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging. To run CI, PR reviewers can do one of these:
🚀 |
Any end-to-end performance benchmark? |
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.
Can you post an end-to-end performance benchmark?
These configs are usually tuned on a gpu by gpu basis.
Is it true that GH200 only comes in single or dual device configurations? So in order to fit deepseek v3 (assuming this since you specify block_shape 128x128) you would need 5 nodes (2xGH200) or 10 nodes (1xGH200) distributed? |
We have a configuration with multiple nodes connected over Inifinband. Tested this on a 8 nodex (each with 1xGH200) - can get around 25-27 tokens per second |
I am not sure I can do a full e2e perf for all the configs. I am only able to test for 2 of them - the fused_moe and the N=576,K=7168 for the quant config. Should I revert the rest from this PR? |
The H200 configs work for the GH200 (it has 92GB gpu memory).