[go: up one dir, main page]

Skip to content
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

Fix using VAE in quantization mode #1090

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ccssu
Copy link
Contributor
@ccssu ccssu commented Aug 23, 2024

Summary by CodeRabbit

  • New Features
    • Introduced a new method for handling VAE models in the booster quantization process, with a warning about current limitations.
  • Bug Fixes
    • Removed outdated checks and simplified backend handling in model processing.

Copy link
Contributor
coderabbitai bot commented Aug 23, 2024

Walkthrough

Recent changes in the codebase involve the removal of conditional logic concerning the OneFlow backend in booster_cache.py, leading to a simplified model processing flow. Additionally, booster_quantization.py has been updated to include a new method for handling the VAE class, with an explicit warning about its quantization limitations. These modifications affect how models interact with different backends and enhance the execute method for VAE instances.

Changes

Files Change Summary
onediff_comfy_nodes/modules/booster_cache.py, onediff_comfy_nodes/modules/oneflow/booster_quantization.py Significant modifications include the removal of OneFlow backend checks and conditional logic in booster_cache.py, and the addition of a new execute method for VAE instances in booster_quantization.py, addressing quantization support.

Poem

🐇 In the code where logic flowed,
A shift occurred, the backends glowed.
With VAE now in focus bright,
Quantization brings new insight.
Hopping forth, the changes cheer,
A simpler path, we hold so dear! 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor
@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6fe6fdd and df1c9c5.

Files selected for processing (2)
  • onediff_comfy_nodes/modules/booster_cache.py (2 hunks)
  • onediff_comfy_nodes/modules/oneflow/booster_quantization.py (3 hunks)
Additional context used
Ruff
onediff_comfy_nodes/modules/oneflow/booster_quantization.py

135-135: No explicit stacklevel keyword argument found

(B028)

Additional comments not posted (2)
onediff_comfy_nodes/modules/booster_cache.py (1)

54-64: Evaluate the impact of removing OneFlow backend checks.

The removal of OneFlow backend checks simplifies the code but may affect functionality related to caching and backend compatibility. Ensure that this change aligns with the overall architectural goals and does not introduce regressions.

Consider verifying the impact of these changes on the system's behavior, especially in environments where OneFlow might be used.

onediff_comfy_nodes/modules/oneflow/booster_quantization.py (1)

130-139: Ensure the new VAE handling aligns with quantization objectives.

The new method for handling VAE in the execute method is a valuable addition. Ensure that this approach aligns with the overall quantization strategy and does not introduce inconsistencies.

Consider testing the behavior of this method with various VAE models to ensure it functions as expected.

Tools
Ruff

135-135: No explicit stacklevel keyword argument found

(B028)

Comment on lines +130 to +139
@execute.register(VAE)
def _(self, model: VAE, **kwargs):
# TODO: VAE does not support quantization and patch compatibility
from .booster_basic import BasicOneFlowBoosterExecutor

warnings.warn(
"TODO: VAE does not support quantization and patch compatibility",
UserWarning,
)
return BasicOneFlowBoosterExecutor().execute(model, **kwargs)
Copy link
Contributor

Choose a reason for hiding this comment

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

Add stacklevel to the warning for better traceability.

The warning about VAE not supporting quantization lacks a stacklevel argument, which could help identify where the warning originates.

Apply this diff to improve the warning:

 warnings.warn(
     "TODO: VAE does not support quantization and patch compatibility",
     UserWarning,
+    stacklevel=2
 )
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
@execute.register(VAE)
def _(self, model: VAE, **kwargs):
# TODO: VAE does not support quantization and patch compatibility
from .booster_basic import BasicOneFlowBoosterExecutor
warnings.warn(
"TODO: VAE does not support quantization and patch compatibility",
UserWarning,
)
return BasicOneFlowBoosterExecutor().execute(model, **kwargs)
@execute.register(VAE)
def _(self, model: VAE, **kwargs):
# TODO: VAE does not support quantization and patch compatibility
from .booster_basic import BasicOneFlowBoosterExecutor
warnings.warn(
"TODO: VAE does not support quantization and patch compatibility",
UserWarning,
stacklevel=2
)
return BasicOneFlowBoosterExecutor().execute(model, **kwargs)
Tools
Ruff

135-135: No explicit stacklevel keyword argument found

(B028)

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.

1 participant