Skip to content

GLM-4 Update #20736

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

Merged
merged 53 commits into from
Jul 19, 2025
Merged

GLM-4 Update #20736

merged 53 commits into from
Jul 19, 2025

Conversation

zRzRzRzRzRzRzR
Copy link
Contributor

GLM-4 Update of Moe Support

Signed-off-by: zRzRzRzRzRzRzR <[email protected]>
Copy link

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

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 either: Add ready label to the PR or enable auto-merge.

🚀

Copy link
Contributor

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

Choose a reason for hiding this comment

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

Summary of Changes

Hello @zRzRzRzRzRzRzR, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces comprehensive support for the GLM-4 Mixture-of-Experts (MoE) model within vLLM. It provides the full architectural implementation, including specialized MoE components, and integrates the new model into the existing benchmarking and model loading infrastructure.

Highlights

  • New Model Support: I've added the complete implementation for the Glm4MoeForCausalLM model architecture, enabling vLLM to support GLM-4 Mixture-of-Experts models.
  • Mixture-of-Experts (MoE) Implementation: The new glm4_moe.py file includes custom components like Glm4MoeTopkRouter for expert selection and Glm4MoeSparseMoeBlock to handle the specific routing and shared expert mechanisms of GLM-4's MoE architecture.
  • System Integration: Updates were made to the MoE benchmarking script (benchmark_moe.py) and the model registry (registry.py) to properly recognize and integrate the new Glm4MoeForCausalLM model within vLLM's ecosystem.
  • Weight Loading Logic: The new model implementation includes robust weight loading logic to correctly map and load parameters from HuggingFace checkpoints, covering stacked linear layers (QKV, gate/up projections) and individual expert weights.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@mergify mergify bot added the performance Performance-related issues label Jul 10, 2025
Copy link
Contributor

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

Choose a reason for hiding this comment

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

Code Review

The pull request adds support for GLM-4 MoE models to vLLM. The changes include modifying the benchmark script to include GLM-4 MoE, adding the GLM-4 MoE model to the model registry, and creating a new file for the GLM-4 MoE model architecture. There's a potential typo in the benchmark script that needs to be addressed, and the model path in the registry should be a real model name.

Signed-off-by: zRzRzRzRzRzRzR <[email protected]>
Signed-off-by: zRzRzRzRzRzRzR <[email protected]>
@mergify mergify bot added the new-model Requests to new models label Jul 10, 2025
Copy link
Collaborator

@jeejeelee jeejeelee left a comment

Choose a reason for hiding this comment

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

Thank you, we also need to update the document.

@zRzRzRzRzRzRzR
Copy link
Contributor Author

Thank you, we also need to update the document.

Thank you, we also need to update the document.

you mean supported_models.md, isnt it generate auto?

@jeejeelee
Copy link
Collaborator

Thank you, we also need to update the document.

Thank you, we also need to update the document.

you mean supported_models.md, isnt it generate auto?

Yes, we need to update manually.

@zRzRzRzRzRzRzR
Copy link
Contributor Author

We also have the MTP model, but if this PR meets the requirements, it can be merged first. The implementation of MTP can be proposed in a separate PR.

@zRzRzRzRzRzRzR
Copy link
Contributor Author

This seems to be due to the example model not being released, making it impossible to find, or is it an error with the VoxtralForConditionalGeneration model? @DarkLight1337

@DarkLight1337
Copy link
Member

DarkLight1337 commented Jul 19, 2025

You can ignore the problem related to Voxtral. However, the GLM-4-MoE-MTP model is also failing the test which needs to be fixed here

@zRzRzRzRzRzRzR
Copy link
Contributor Author

AssertionError: function <function can_initialize at 0x7ff0e802a520> failed when called with args ('Glm4MoeMTPModel', <_pytest.monkeypatch.MonkeyPatch object at 0x7ff2635270e0>, <tests.models.registry.HfExampleModels object at 0x7ff0ea18aae0>) and kwargs {}

I only seem to have found this one error related to GLM-4-MoE. But is this caused by the model being too large? It looks like the error is because the model can’t be found. Our model hasn’t been open-sourced yet, and the model is indeed named GLM-4.5.

ERROR 07-19 05:12:42 [config.py:129] Error retrieving file list: (MaxRetryError("HTTPSConnectionPool(host='huggingface.co', port=443): Max retries exceeded with url: /api/models/THUDM/GLM-4.5/tree/main?recursive=True&expand=False (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fa5e4e76170>: Failed to establish a new connection: [Errno 101] Network is unreachable'))"), '(Request ID: 1c6445ab-986e-4e61-ac9f-964c2099442e)'), retrying 1 of 2

@DarkLight1337
Copy link
Member

If the checkpoint is not released yet, set is_available_offline=False for that model in the registry

Copy link

mergify bot commented Jul 19, 2025

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @zRzRzRzRzRzRzR.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

@mergify mergify bot added the needs-rebase label Jul 19, 2025
@DarkLight1337
Copy link
Member

Sorry there are more conflicts now that need to be solved

@zRzRzRzRzRzRzR
Copy link
Contributor Author

done and test again

@mergify mergify bot removed the needs-rebase label Jul 19, 2025
@zRzRzRzRzRzRzR
Copy link
Contributor Author

@DarkLight1337 Now it is not GLM-MoE Error

@DarkLight1337
Copy link
Member

@zRzRzRzRzRzRzR
Copy link
Contributor Author

Let me try again, I modified some local files. It seems there are only errors from llama3.2 left. I'm really not very familiar with this part of the code.

Copy link
Collaborator

@Isotr0py Isotr0py left a comment

Choose a reason for hiding this comment

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

LGTM if all tests can pass. Assuming that model outputs are aligned on your side.

@Isotr0py Isotr0py enabled auto-merge (squash) July 19, 2025 16:08
Copy link
Member

@DarkLight1337 DarkLight1337 left a comment

Choose a reason for hiding this comment

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

Same, thanks for working on this!

@Isotr0py Isotr0py merged commit 10eb24c into vllm-project:main Jul 19, 2025
74 checks passed
@zRzRzRzRzRzRzR zRzRzRzRzRzRzR deleted the glm-moe branch July 20, 2025 03:07
@zRzRzRzRzRzRzR zRzRzRzRzRzRzR restored the glm-moe branch July 21, 2025 13:26
@zRzRzRzRzRzRzR zRzRzRzRzRzRzR deleted the glm-moe branch July 21, 2025 13:26
LyrisZhong pushed a commit to LyrisZhong/vllm that referenced this pull request Jul 23, 2025
Signed-off-by: zRzRzRzRzRzRzR <[email protected]>
Signed-off-by: Isotr0py <[email protected]>
Signed-off-by: Lu Fang <[email protected]>
Co-authored-by: Isotr0py <[email protected]>
Co-authored-by: Lu Fang <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation frontend new-model Requests to new models performance Performance-related issues ready ONLY add when PR is ready to merge/full CI is needed speculative-decoding tool-calling
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

5 participants