Skip to content

[Examples] [Bugfix] skip sparsity stats when saving checkpoints #1528

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 2 commits into from
Jun 10, 2025

Conversation

kylesayrs
Copy link
Collaborator

@kylesayrs kylesayrs commented Jun 9, 2025

Purpose

  • Fix example failure where sparsity stats were attempted to be computed on a compressed model
    • This happened because the get_model_compressor cannot compute sparsity stats of a compressed model

Prerequisites

Changes

  • When saving checkpoints, call get_model_compressor on the decompressed model (before it is compressed, not after)
  • Do not save checkpoints with sparsity stats by default, due to high runtime

Testing

  • Ran example to completion with reduced training duration

Signed-off-by: Kyle Sayers <kylesayrs@gmail.com>
Copy link

github-actions bot commented Jun 9, 2025

👋 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.

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 @kylesayrs, 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 addresses a bug encountered in examples where saving checkpoints of compressed models failed due to an inability to compute sparsity statistics on the compressed state. It resolves this by adjusting the order of operations during checkpoint saving to ensure the model compressor is obtained on the decompressed model. Additionally, it changes the default setting for skipping sparsity statistics during saves to True to improve performance.

Highlights

  • Bugfix for Checkpoint Saving: Fixed an issue where attempting to compute sparsity statistics on a compressed model during checkpoint saving would fail. The logic to obtain the model compressor is now performed before the model is potentially compressed for saving, ensuring it operates on the decompressed state.
  • Default Behavior Change: Changed the default value for skip_sparsity_compression_stats to True when saving models/checkpoints. This avoids the potentially high runtime cost associated with computing sparsity statistics by default.
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 configureGemini 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 addresses a bug by ensuring get_model_compressor is called on the model before it's potentially compressed by save_pretrained when saving checkpoints. It also changes the default to skip sparsity stats computation during this process to avoid high runtime costs. The feedback provided aims to improve the clarity of comments.

@rahul-tuli
Copy link
Collaborator

Lgtm, could you also update the save_pretrained readme in the docs folder

@kylesayrs kylesayrs added the ready When a PR is ready for review label Jun 9, 2025
@kylesayrs kylesayrs changed the title [Example] [Bugfix] skip sparsity stats when saving checkpoints [Examples] [Bugfix] skip sparsity stats when saving checkpoints Jun 9, 2025
Copy link
Collaborator

@rahul-tuli rahul-tuli left a comment

Choose a reason for hiding this comment

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

@kylesayrs
Copy link
Collaborator Author

@rahul-tuli I've read through the docs and don't see the section you want updated? Afaict these docs are for users who want help calling save_pretrained themselves. I'm not sure how these changes are related or relevant to that reader?

@rahul-tuli
Copy link
Collaborator

rahul-tuli commented Jun 9, 2025

@rahul-tuli I've read through the docs and don't see the section you want updated? Afaict these docs are for users who want help calling save_pretrained themselves. I'm not sure how these changes are related or relevant to that reader?

My bad @kylesayrs meant to request a change on #1530
And, missed the filename, thought you were making changes to save_pretrained_wrapper but this is a different pathway altogether. This is good to go from my side!

@kylesayrs kylesayrs enabled auto-merge (squash) June 10, 2025 19:30
@kylesayrs kylesayrs merged commit dc2e9b0 into main Jun 10, 2025
11 checks passed
@kylesayrs kylesayrs deleted the kylesayrs/bugfix-training-checkpoint-saving branch June 10, 2025 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready When a PR is ready for review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants