Skip to content

Conversation

@phaelon74
Copy link

SUMMARY:
Without a model file for GLM, only experts activated from a calibaration sample, are used. This means accuracy will drop quite a bit if the dataset is not robust and even with a robust dataset, I highly doubt all experts are being hit and pulled from as needed.

With this model file, it should cycle through all experts like Qwen does with it's model files, etc.

TEST PLAN:
I used LLM_Compressor to quant GLM4.7 and it succeeded without issue. Equally I quanted a llama3 model as well, to make sure it didn't break any other flows.

@github-actions
Copy link

👋 Hi! Thank you for contributing to llm-compressor. Please add the ready label when the PR is ready for review.

Note: This is required to complete the testing suite, please only add the label once the PR is code complete and local testing has been performed.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @phaelon74, 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 a specialized calibration module for GLM4 Mixture-of-Experts (MoE) models within the llmcompressor framework. The primary goal is to enhance the accuracy and robustness of quantized GLM4 models by ensuring that all experts within the MoE architecture are thoroughly calibrated, rather than just those activated by a limited calibration sample. This is achieved by temporarily routing all tokens to all experts during the calibration phase, while still respecting routing weights for the final output.

Highlights

  • GLM4 MoE Calibration Module: A new CalibrationGlm4MoeMoE module has been introduced to enable proper calibration for GLM4 Mixture-of-Experts (MoE) models. This module ensures that during calibration, all tokens are sent to all experts, allowing for comprehensive quantization statistics collection, even for experts not activated by standard routing.
  • Enhanced Calibration Accuracy: This change addresses a limitation where, without a dedicated model file, only experts activated by a calibration sample were used, potentially leading to reduced accuracy. The new module ensures all experts are properly calibrated, improving the overall robustness and accuracy of quantized GLM4 models.
  • Integration and Testing: The new GLM4 MoE calibration module is integrated into the llmcompressor.modeling package. Testing confirmed successful quantization of GLM4.7 and verified that existing quantization flows for other models like Llama3 remain unaffected.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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.

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

This pull request adds support for GLM MoE model calibration by introducing CalibrationGlm4MoeMoE. The implementation correctly handles passing all tokens to all experts during calibration, which is crucial for accurate quantization. My feedback includes a suggestion to refactor the forward method to improve maintainability and a strong recommendation to add unit tests for this new functionality to ensure its correctness and prevent future regressions.

@mratsim
Copy link
Contributor

mratsim commented Dec 27, 2025

Nice, you frontrunned me!

I was tired of waiting for Transformers v5 before doing proper all experts calibration of GLM-4.7 / GLM-4.5-Air / GLM-4.6V (see #2036).

Not doing so can have a dramatic impact and many models out there just use raw LLM compressors (mine included): https://avtc.github.io/aquarium-side-by-side/

image

@mratsim
Copy link
Contributor

mratsim commented Dec 27, 2025

By the way, does this PR work on the vision models as-is like GLM-4.6V?

@phaelon74
Copy link
Author

By the way, does this PR work on the vision models as-is like GLM-4.6V?

It should handle it yes, schematically, but I can run it through the test script later tonight and tell you for certain.

@phaelon74
Copy link
Author

I believe this is now ready for formal review, after having resolved the issues and added a testing script with results. This is my first PR, so if I missed anything, apologies.

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.

2 participants